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 skills add kitchen-engineer42/joharnessburg --skill plan-md-authoringgit clone --depth 1 https://github.com/kitchen-engineer42/joharnessburgWrote 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/skills/kitchen-engineer42/joharnessburg/plan-md-authoring)<a href="https://agentmods.dev/skills/kitchen-engineer42/joharnessburg/plan-md-authoring"><img src="https://agentmods.dev/badge/skills/kitchen-engineer42/joharnessburg/plan-md-authoring/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/skills/kitchen-engineer42/joharnessburg/plan-md-authoring"><img src="https://agentmods.dev/badge/skills/kitchen-engineer42/joharnessburg/plan-md-authoring.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.00105 | $0.02325 |
| Opus 5 | $0.00053 | $0.01162 |
| Sonnet 5 | $0.00021 | $0.00465 |
| Haiku 4.5 | $0.00011 | $0.00232 |
Grade A, and why
plan-md-authoring 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 9d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-md-authoring
You are writing PLAN.md for the first time on a new John project. After this, [[plan-md-evolution]] takes over — this skill is just the bootstrap.
The plan is not a recipe. It's a wide-tunnel agreement between you and the user about what's being built, how the work decomposes into phases, and where the open decisions are. Too narrow and you'll regret it in two phases when the corpus surprises you. Too loose and you'll re-derive everything every iteration.
When to start writing
After /john:init has scaffolded <project>/.john/ and put the user's input materials in <project>/.john/input/. Before you've parsed anything. Before you've decided on a knowledge schema.
The plan should be written through a conversation with the user, not generated unilaterally. If you find yourself filling in sections without asking, stop and ask. You only get one chance to shape a project at the top — don't waste it on assumptions.
The skeleton
PLAN.md has these sections in this order. Some come from your conversation with the user; some you fill in as the project progresses.
# PLAN.md — <project name>
## Project intent
<what the produced app does, who uses it, what it consumes, what success looks like>
## Knowledge inventory (from the knowledge phases)
<initial: pointer to .john/input/ and a one-line corpus profile
over time: pointers to <project>/.claude/skills/ and <project>/.agents/skills/ once the knowledge phases ship>
## App-type definition
- Knowledge format: <facts? rules? stories? wiki? mixed? — initial guess, may evolve>
- Knowledge schema: <starter sketch; expect to iterate>
- App mechanism: <how the produced app works for end-users>
- Build pipeline: <the rest of this doc — phases that build the app>
## Phases
### Phase 1: <name>
- Intent: <one sentence>
- Subagent assignments: <if vertical fan-out, what's the unit?>
- Execution: <Workflow yes/no; if yes: worker agent + cross-check agent + model — see [[vertical-workflows]]>
- Skills to invoke: <[[skill-1]], [[skill-2]]>
- Required artifacts (disk-verifiable): <paths the engine can check>
- Done criteria: <observable conditions; not "feels finished">
### Phase 2: ...
...
## Subagent matrix
<for any phase with vertical fan-out, the list of work units and current state.
may be empty at first, fills in as phases hit fan-out points>
## Open decisions
<things you want the user to weigh in on before you barrel forward>
## Log
<append-only, most recent first. dated entries:
- phase advances ("Phase 2 done, X artifacts produced")
- decisions you made and why
- blockers you wrote to "Open decisions"
- user instructions received mid-flight>
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.
- 9d ago First seen · 139 lines · 105 tokens per session scan A ce6e4d21e2b9
plan-md-authoring is a skill published in the GitHub repository kitchen-engineer42/joharnessburg (9 stars, last pushed 2mo ago), licensed MIT. It adds 105 tokens to every session and 2,325 once invoked, about $0.0005 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 skills, from other repositories
docs-drift
Documentation-drift audit for this plugin monorepo. Audit either each scoped plugin's unreleased changelog claims or its latest shipped release from the previous reachable plugin-name--v tag, then verify that plugin READMEs, docs, CLAUDE.md or AGENTS.md files, and root documentation tell the truth for the matching…
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
test-run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.