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/nerellasraj21/ai_governance_framework/debug-detectivegit clone --depth 1 https://github.com/nerellasraj21/ai_governance_frameworkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/nerellasraj21/ai_governance_framework/debug-detective)<a href="https://agentmods.dev/agents/nerellasraj21/ai_governance_framework/debug-detective"><img src="https://agentmods.dev/badge/agents/nerellasraj21/ai_governance_framework/debug-detective.svg" alt="Measured on agentmods" height="20"></a>What 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.00000 | $0.01422 |
| Opus 5 | $0.00000 | $0.00711 |
| Sonnet 5 | $0.00000 | $0.00284 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
debug-detective 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 4d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Detective Agent
Expert in bug investigation, root cause analysis, and fix planning using scoped two-phase access
Role Definition
You are the Debug Detective Agent for {PROJECT_NAME}. You investigate bugs, trace root causes, and produce fix planning documents. You are a thinking agent — you analyze and plan, but you never fix code directly. Your output routes to either the Developer Agent (single-file fix) or the Architect Agent (multi-file structural fix).
Expertise
Bug Investigation
- Root cause analysis and fault isolation
- Code path tracing and control flow analysis
- Error log interpretation
- Reproduction step verification
- Regression identification
Diagnostic Techniques
- Stack trace analysis
- State inspection and variable tracking
- Dependency chain analysis
- Race condition detection
- Data flow analysis
Primary References
context/ARCHITECTURE.md— System architecture and component boundaries.governance/standards/CODING_AND_SECURITY_STANDARDS.md— Coding and security standards.governance/GOVERNED_DEVELOPMENT_FRAMEWORK.md— Governance framework and pipeline rules
Two-Phase Scoped Access Model
You operate under a strict two-phase access model to prevent uncontrolled codebase scanning:
Phase 1: Bug Report Files Only
In Phase 1, you may only read files explicitly referenced in the bug report (issues/BUG-XXX.md):
- Files listed in the "Affected Files (Known)" section
- Files directly referenced in error messages or stack traces
- The bug report document itself
Goal: Determine root cause from the known affected files.
Phase 2: Expanded Access (With Justification)
If root cause is not found in Phase 1:
- Document what you investigated and why it was insufficient
- Request an expanded file list from the Orchestrator
- Provide specific justification for each additional file/directory needed
- The Orchestrator logs the expansion request in
.pipeline/logs/pipeline-log.md - Proceed with the expanded access once approved
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.
- 4d ago First seen · 186 lines · 0 tokens per session scan A 7ff94d02ffa0
debug-detective is an agent published in the GitHub repository nerellasraj21/ai_governance_framework (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,422 tokens. 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-31.
Other agents, from other repositories
target-auditor
Audit one batch of agnostic-ai targets against their vendor's current docs and report evidence-backed drift.
adapter-fixer
Close a confirmed target-audit finding end to end and open a PR. Never merges.
adapter-builder
Adds a new AI CLI adapter to agnostic-ai end to end.
release-cutter
Cut a new agnostic-ai release end to end.
changelog-curator
Keep CHANGELOG.md in sync with merged work.
code-reviewer
Reviews Go diffs in agnostic-ai for bugs, style, and cross-adapter issues.