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/openplanr/planr-pipelineWrote 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/commands/openplanr/planr-pipeline/audit)<a href="https://agentmods.dev/commands/openplanr/planr-pipeline/audit"><img src="https://agentmods.dev/badge/commands/openplanr/planr-pipeline/audit/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/commands/openplanr/planr-pipeline/audit"><img src="https://agentmods.dev/badge/commands/openplanr/planr-pipeline/audit.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.00000 | $0.04363 |
| Opus 5.5 | $0.00000 | $0.01745 |
| Sonnet 5.5 | $0.00000 | $0.00873 |
| Haiku 4.5 | $0.00000 | $0.00436 |
Grade A, and why
audit scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bash(curl:*): ❌ This is a copy
100% identical to audit — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
planr-pipeline & OpenPlanr — Master Codebase Audit Prompt
For use in Claude Code / any agentic coding environment
Drop this as a slash command or paste directly into Claude Code
You are a Principal Engineer & Product Architect conducting a full adversarial audit of this codebase. Your job is not to be polite. Your job is to find every structural, architectural, and experiential problem — then produce an actionable plan to fix them.
This audit has three phases. You must complete them in order. Do not skip phases. Do not summarize — produce full deliverables.
PHASE 1 — DISCOVERY (Read-Only)
Scan the entire repository. Read every file. Build a mental model before drawing conclusions.
1.1 Structure Inventory
Run the following and record the output:
find . -type f | grep -v node_modules | grep -v .git | sort
Then map the tree into categories:
- Entry points (CLI commands, slash commands)
- Agent definitions
- Shared utilities / helpers
- Config / schema files
- Templates
- Documentation
- Tests
- Generated / output artifacts
1.2 Complexity Heatmap
For every source file, record:
- Line count
- Number of functions / exported symbols
- Number of external imports
- Cyclomatic complexity (estimate from nesting depth)
Flag any file over 300 lines as a bloat candidate. Flag any file over 500 lines as a critical bloat violation.
1.3 Dependency Audit
Read package.json (and any sub-package manifests). For every dependency, ask:
- Is it actually used? (grep for import/require)
- Could it be replaced by a built-in Node/TypeScript equivalent?
- Is it a heavy library doing a job that needs 10 lines of code?
- Is it pinned to a specific version? Is that version current?
Flag every unused or replaceable dependency as a dead weight item.
1.4 Schema & Contract Audit
Locate every schema definition (Zod, TypeScript interfaces, JSON schema, frontmatter contracts). For each:
- Is the schema co-located with its consumer, or floating?
- Is it validated at runtime or only at compile time?
- Is there a single source of truth, or duplicates?
- Is the schema versioned?
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.
- 1mo ago First seen · 420 lines · 0 tokens per session scan A 206664d90272
audit is a command published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,363 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to audit, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
recover
Diagnose and recover from interrupted or corrupted state.
analyze-misfires
Identify skills injected where not needed, propose regex and description tightening.
codebase-audit
Read-only codebase survey — a prioritized, evidence-backed review report of what is worth doing. Use standalone or before /iteration-start; scope keywords pick the effort level and focus. Never edits source.
bugfix
TDD-driven bugfix workflow: tester writes failing test (RED) → developer fixes (GREEN) → developer refactors (REFACTOR) → reviewer validates. Accepts issue number, description, or both. Asks before pushing and creating a PR; --no-pr commits locally without asking.
review
Review branch changes against Archcore docs, or report project health; drift runs staleness detection, deep a full documentation audit, closeout closes a finished feature, experience captures a repeated pattern.