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/kitchen-engineer42/joharnessburg/reportgit 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/commands/kitchen-engineer42/joharnessburg/report)<a href="https://agentmods.dev/commands/kitchen-engineer42/joharnessburg/report"><img src="https://agentmods.dev/badge/commands/kitchen-engineer42/joharnessburg/report.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.00086 | $0.00605 |
| Opus 5 | $0.00043 | $0.00302 |
| Sonnet 5 | $0.00017 | $0.00121 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
report 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 5d 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
When this command fires:
-
Run the process scorecard via Bash (add
--applied-metadata ${CLAUDE_PLUGIN_ROOT}/.applied-metadata.jsonwhen running under an applied template — that file sits at the merged plugin's root):python3 "${CLAUDE_PLUGIN_ROOT}/scripts/process_scorecard.py"On
success: false("No .john/ directory"), tell the user there's no workspace to report on —/john:initfirst.Then emit the auditor manifests (idempotent, zero-token; same
--applied-metadatanote as above):python3 "${CLAUDE_PLUGIN_ROOT}/scripts/emit_manifests.py" --applied-metadata "${CLAUDE_PLUGIN_ROOT}/.applied-metadata.json"This writes
<project>/.john/PROVENANCE.json(run identity — John version, template name+version, corpus inputs, observed phases, run window) andSELF_EVAL_MANIFEST.json(how to re-run the scorecard, where reports live), so the finished run is legible to an external auditor and John's own evolution tooling without reading app code. A missing.applied-metadata.jsonis fine — a vanilla run emits both with template fields null. (Where a produced app wrote its results is template-defined; John core does not emit that manifest.) -
Assemble the report at
<project>/.john/reports/<YYYY-MM-DD>-run-report.md, following the format in theskill-evolutionskill'sreferences/run-report-format.md(1 page: manifest, scorecard highlights, outcome summary, candidate lessons, deviations). Create thereports/directory if missing. The scorecard JSON is the evidence backbone; your judgment supplies the outcome summary and the lesson selection — pick the few lessons whosescope_guessistemplateorcoreand whose evidence held up. -
Walk the scrub-and-generalize checklist (bottom of the format reference) over the draft — the report is built to LEAVE this project, so it must carry no corpus content, client identifiers, or local filesystem paths. Restate any lesson that fails the check so it would hold for the next corpus of the domain.
-
Show the user the report path and the highlights. Remind them: sharing is manual and theirs — typically to the template's owner as evolution evidence. Nothing is ever transmitted automatically.
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.
- 5d ago First seen · 28 lines · 86 tokens per session scan A b4e7429a0f00
report is a command published in the GitHub repository kitchen-engineer42/joharnessburg (9 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 605 once invoked, about $0.0004 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
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
save
Save this conversation as a new or existing reusable context.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.