Back to skill

Security audit

FOSMVVM Fields Generator

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documentation-only code generation guide for FOSMVVM form-field templates, with no hidden execution, persistence, or sensitive access behavior found.

Before installing, treat this as a Swift/FOSMVVM template helper. Review generated files before committing them, and adjust localization blocks to match the languages your project supports.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

This markdown reference includes YAML templates and examples that define only an en: locale for user-facing titles, placeholders, and validation messages. Because the file presents these as complete reference templates and does not mention locale choice, opt-in, or a justified English-only scope, it can encourage a language-default behavior that conflicts with locale-flexibility policy expectations.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The full example's localization file is likewise constrained to the en: locale and contains user-visible strings with no surrounding guidance about selecting or adding other locales. This is a natural-language locale-policy concern because the example can be copied directly into implementations and implicitly standardize English-only output.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.