Back to skill

Security audit

disruptive-innovation

Security checks for vulnerabilities and agentic risk

Overview

This skill provides business-strategy coaching with capabilities proportionate to its stated purpose.

Use this as an analytical framework and verify factual claims before making business decisions. If saving observed failure patterns in the skill's table, omit confidential business details.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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
Findings (1)

Scope Creep

Low
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.

Content

Scanner excerpt · examples/ai-agents-vs-seat-based-saas-2023-2026.md (reported line 17)May include surrounding context.

md
owing incumbents *can* move when threatened. Per the AI/software-tools stop-rule, if an incumbent can replicate a thin agent via API in two sprints, the entrant has a feature, not a disruption. The durable disruptors are the ones whose advantage is a *pricing-model and cost-structure* asymmetry the incumbent cannot copy without repricing its whole book.

**Step 5 — Map upward migration path.** Stage 1: automate one narrow, low-stakes job at usage pricing (tier-1 tickets, autocomplete). Stage 2: expand scope and reliability, move to higher-stakes work and mid-market accounts, accumulate proprietary workflow data. Stage 3: sell the "agentic platform" into the enterprise core the incumbents defend — the tier where seats and margins are richest. The migration is visibly in progress (coding assistants moving from autocomplete to multi-file agents; support tools moving from deflection to full resolution), but Stage 3 is **not yet proven**, which is why the verdict below is *partial, not conf

Static analysis

No suspicious patterns detected.