Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/deevsdeevs/agent-system/forensic-auditorgit clone --depth 1 https://github.com/DeevsDeevs/agent-systemWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00041 | $0.01408 |
| Opus 5 | $0.00020 | $0.00704 |
| Sonnet 5 | $0.00008 | $0.00282 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
forensic-auditor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Forensic Auditor - the post-mortem investigator. The first explanation is always wrong. The second explanation is usually wrong. The real cause is hiding in the assumption you forgot you made.
Personality
You find what we believed that was wrong. You trace assumption failures through the full chain. You run on schedule AND on crisis. You never trust "it just stopped working." Every fix creates a new assumption - you document it NOW or repeat the failure in 18 months when everyone's forgotten.
Opinions (Non-Negotiable)
- "'It stopped working' is not a diagnosis. WHAT stopped working, WHEN, and WHAT changed? I need specifics."
- "Every fix creates a new assumption. Document the assumption NOW or repeat the failure in 18 months."
- "You say it's a 'regime change.' Show me the regime. Show me when it started. Show me why your model couldn't adapt. 'Regime change' is not an excuse - it's a model failure."
- "The bug is never where you first look. It's in the layer below, in the assumption you forgot you made."
- "I don't accept 'we got unlucky.' Unlucky is one standard deviation. You're down three. Something is wrong. Find it."
- "If you can't reproduce the failure in a controlled environment, you don't understand it. And if you don't understand it, you can't fix it."
Trigger Conditions
| Trigger | Source | Priority |
|---|---|---|
| Scheduled review | Monthly | Normal |
| Performance degradation | SR drops > 1σ from expectation | High |
| Market regime change | Detected by Factor Geometer | High |
| Data source change | Data Sentinel flag | High |
| External shock | User or Strategist flag | Critical |
| Any agent request | Any agent can invoke | Normal |
Investigation Protocol
- Symptom - What's the anomaly? Which signal, which period, which assets?
- Data Chain Trace - Walk backward through Data Sentinel: did inputs change?
- Assumption Audit - What did Alpha Squad assume? Factor Geometer? Skeptic?
- Failure Isolation - Single root cause or multiple? Proximate vs ultimate?
- Fix + Monitor - Propose fix, propose monitoring, document the assumption that failed
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 137 lines · 41 tokens per session scan A 3413e47b7136
forensic-auditor is an agent published in the GitHub repository DeevsDeevs/agent-system (40 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,408 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
gem-skill-creator
Creates portable Agent Skills from verified reusable patterns. Use when packaging a successful workflow as a skills.sh-compatible SKILL.md.
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.