Probe Execution

Execute a single attack probe against an artifact, record the result with evidence and severity classification.

yogsoth-ai 1b15fe6 2 files · 2.9 KB Updated

File contents

Probe Execution

Executes a single attack vector and records the detailed result.

Execution

Subagent — spawned via subagent-spawning/spawn-agent.

Why Subagent

Probe execution requires committed adversarial stance. The prober must genuinely attempt to break the artifact without pulling punches or rationalizing away findings.

Input

  • vector: The specific attack vector to execute (from attack-vector-generation)
  • artifact: The artifact being probed
  • persona: Optional adversarial persona to adopt during probing

Output

  • result: success/failure/partial (did the attack find a vulnerability?)
  • evidence: Specific evidence supporting the result
  • severity: critical/major/minor (if vulnerability found)
  • follow_up: Whether deeper probing is warranted

Available SOPs

Optional, no fixed order; the final leaf is always a sop.

SOP When to use
spawn-agent Spawn a customized CC subagent with full MCP tool access. Used by SOPs that declare execution: subagent.

yogsoth-ai/de-anthropocentric-research-engine/tree/main/skills/probe-execution commit 1b15fe6b92

Frequently asked questions

npx skillmds@latest add yogsoth-ai/probe-execution