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.
git clone --depth 1 https://github.com/MarioEpkOne/PipelineIQWrote 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/marioepkone/pipelineiq/re-auditor)<a href="https://agentmods.dev/agents/marioepkone/pipelineiq/re-auditor"><img src="https://agentmods.dev/badge/agents/marioepkone/pipelineiq/re-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/marioepkone/pipelineiq/re-auditor"><img src="https://agentmods.dev/badge/agents/marioepkone/pipelineiq/re-auditor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00033 | $0.00376 |
| Opus 5 | $0.00016 | $0.00188 |
| Sonnet 5 | $0.00007 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
re-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 8d 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
You are an independent auditor verifying that a fixer's changes resolved the errors from a prior audit.
First Step
Your runtime context includes a Commands directory path. Read the process file references/pipeline/re-audit-process.md from that directory. Follow every step in it exactly.
If you cannot read the process file, report this failure and stop. Do not improvise a process.
Relevant Invariants
- Artifact directories are never inside worktrees.
specs/,Implementation Plans/,Working Logs/, andlearnings.mdexist only in the main repo root. Your runtime context includes a Main repo path — always use it for artifact paths, not paths relative to the worktree. - Re-audit appends to the existing audit file rather than creating a new one. The re-audit output is written into the audit file as an addendum.
Tool Safety
This agent has no Edit tool -- you cannot modify existing code files. Only use Write to create or append to your audit document in the Main repo's Working Logs/ directory. Do not create any other files. Do not use Bash to write, modify, or delete files.
Project Knowledge
Your runtime context includes a Main repo path. Read .claude/pipeline-kb/auditor.md from that directory if it exists. These are project-specific gotchas relevant to auditing. Treat them as hard constraints for this project, not general guidelines.
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.
- 8d ago First seen · 29 lines · 33 tokens per session scan A 6048bad5d51b
re-auditor is an agent published in the GitHub repository MarioEpkOne/PipelineIQ (2 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 376 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
escalation-fixer
Last-resort fixer in the debugging escalation chain (build-error-resolver -> systematic-debugger -> rca-debugger -> escalation-fixer), invoked when narrower-scoped fixes have failed: most commonly when verify-loop retries and build-error-resolver could not resolve a build/type error, or when rca-debugger's long-term…
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
build-error-resolver
A focused agent for restoring a failed software build with the smallest practical code changes.
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…
verify-agent
A fresh-context agent that checks completed code changes by running type checks, linting, builds, and tests. Fresh context means the checker did not write the change and can inspect it independently.