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 commands/sebyx07/claude-code-bible/planxgit clone --depth 1 https://github.com/sebyx07/claude-code-bibleWrote 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/sebyx07/claude-code-bible/planx)<a href="https://agentmods.dev/commands/sebyx07/claude-code-bible/planx"><img src="https://agentmods.dev/badge/commands/sebyx07/claude-code-bible/planx.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.00031 | $0.00673 |
| Opus 5 | $0.00015 | $0.00336 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
planx 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/planx
Plan only — outline the writing, never write the chapter. No edits outside the plan dir; never touch docs/NN-*.md from here.
Goal
$ARGUMENTS
Steps
- Path.
date +%Y/%m/%d.Glob docs/plans/<YYYY>/<MM>/<DD>/1*→ next1NN(else101). Slug kebab-case, ≤5 words. Dir:docs/plans/<YYYY>/<MM>/<DD>/<1NN>-<slug>/. - Explore.
Task(Explore, "very thorough"): the adjacent chapters, the README TOC row that will change, every cross-link that must be added or updated (grep -rn "NN-"), and the ch. 11 rules the prose must obey. - Write
overview.md— Goal (what the chapter teaches, why it earns a slot) · Placement (chapter number, neighbours, TOC row text) · Section outline (one line per##) · Plan files (numbered) · Done when · Risks. - One
<NN>-<aspect>.mdper section or per file touched —> Part of overview.md. Depends on: <NN or none>.· What to write (bullets, the claims to make) · Sources to verify against · Links to add/update (path→path) · Done when. Never draft the prose here. status.ymlalongsideoverview.md—plan,title,status(not_started|in_progress|blocked|complete|superseded),created_by/ownerfromgit config user.name,worked_by: "",percent: 0,current_focus: "",slices:(one row per<NN>file withstatus/percent),evidence: [],notes: "",last_updated.
Rules
- Compact English, fragments over sentences, tables for structured data — the plan obeys ch. 11 too.
- Reference-only: point at chapters and line numbers, don't paste prose.
- No checkboxes.
status.ymlis the only tracker. - Never plan around git worktrees. The writer works directly in this checkout; parallel agents share it, one chapter file each. Never
isolation: worktree. - Never plan a renumber unless the ask demands it — it rewrites every inter-chapter link.
- Every plan that adds or retitles a chapter includes the README TOC row and cross-link sweep as an explicit slice.
Output
✓ docs/plans/<YYYY>/<MM>/<DD>/<1NN>-<slug>/overview.md + 01-….md, … + status.yml
Next: run a writer on overview.md.
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 · 36 lines · 31 tokens per session scan A da0e0215911b
planx is a command published in the GitHub repository sebyx07/claude-code-bible (5 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 673 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 commands, from other repositories
test
Smart test runner with filtering, coverage, and health monitoring.
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
security-review
Comprehensive security analysis with multi-layer vulnerability detection.
implement-spec
Implement specification with full traceability and test-driven development.
refactor
Interactive refactoring assistant based on Martin Fowler's refactoring catalog.
git-release-workflow
This command has been deprecated and merged into /dev:release.