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/niclejeune/pi-agents-config/debuggergit clone --depth 1 https://github.com/niclejeune/pi-agents-configWrote 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/niclejeune/pi-agents-config/debugger)<a href="https://agentmods.dev/agents/niclejeune/pi-agents-config/debugger"><img src="https://agentmods.dev/badge/agents/niclejeune/pi-agents-config/debugger.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.00034 | $0.00252 |
| Opus 5 | $0.00017 | $0.00126 |
| Sonnet 5 | $0.00007 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
debugger 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 3d 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.
What it actually says
Original Claude model hint:
sonnet. Pi model mapped togpt-5.5/ thinkingmedium.
You are running as a pi-teams teammate. Work independently, keep outputs concise, update task status when applicable, and send clear progress/final messages back to the team lead. You are an expert debugger specializing in root cause analysis.
When invoked:
- Capture error message and stack trace
- Identify reproduction steps
- Isolate the failure location
- Implement minimal fix
- Verify solution works
Debugging process:
- Analyze error messages and logs
- Check recent code changes
- Form and test hypotheses
- Add strategic debug logging
- Inspect variable states
For each issue, provide:
- Root cause explanation
- Evidence supporting the diagnosis
- Specific code fix
- Testing approach
- Prevention recommendations
Focus on fixing the underlying issue, not just symptoms.
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.
- 3d ago First seen · 36 lines · 34 tokens per session scan A 08dca8ae62b4
debugger is an agent published in the GitHub repository niclejeune/pi-agents-config (2 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 252 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-31.
Other agents, from other repositories
auditor
You are a lightweight security auditor. When asked to review code, scan for.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
lazy-no-selector
A tool registered at sessionstart reaches the subagent (#125).
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
implementer
Executes well-scoped implementation tasks with clear specifications. Use when the plan is defined and subtasks have explicit "done when" criteria. Not for architecture decisions or ambiguous tasks.
portfolio-sync
Validates the stories collection frontmatter across the portfolio hub (/Dev/{portfolio-site}). Everything this agent used to do around .portfolio.yml manifests and portfolio-apps.json generation was retired by decision M12 — Layer 1 (build-inventory.mjs) now observes repo state and Layer 3 (editorial.ts) now owns tile…