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 init-workspacegit 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/init-workspace)<a href="https://agentmods.dev/skills/kitchen-engineer42/joharnessburg/init-workspace"><img src="https://agentmods.dev/badge/skills/kitchen-engineer42/joharnessburg/init-workspace.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.1 | $0.00051 | $0.00442 |
| Opus 5 | $0.00026 | $0.00221 |
| Sonnet 5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
init-workspace 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 7d 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
init-workspace
This is the Codex equivalent of Claude Code's /john:init command.
When to use
Use this skill when starting or re-bootstrapping a John project. It creates the project-local John state:
.john/.john/workspace.json.john/input/PLAN.mdCLAUDE.mdif missingAGENTS.mdif missing
Procedure
-
Parse the user's request:
- optional first path: file or directory to copy into
.john/input/ - optional
--force: recreate.john/and regeneratePLAN.md
- optional first path: file or directory to copy into
-
Resolve the plugin root:
- In a Codex plugin install, this skill lives under
<plugin-root>/skills/init-workspace/SKILL.md. - The script is at
<plugin-root>/scripts/init_workspace.py. - In a source checkout, use
plugins/joharnessburg/scripts/init_workspace.py.
- In a Codex plugin install, this skill lives under
-
Run the script from the user's project directory:
python3 "<plugin-root>/scripts/init_workspace.py" <input-path-if-any> <--force-if-present>
-
Parse the JSON on stdout. On success, tell the user:
- project root
.john/created- whether
PLAN.mdwas written or preserved - whether
CLAUDE.mdwas written or preserved - whether
AGENTS.mdwas written or preserved - which input files were copied
-
After success, read the new
PLAN.mdand start the project-shaping conversation usingplan-md-authoring: confirm project intent, decide the app-type definition, and sketch the first phases.
Do not skip step 5. The script only scaffolds; the plan still needs user-facing project decisions.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 53 lines · 51 tokens per session scan A 5d025e6cc2ba
init-workspace is a skill published in the GitHub repository kitchen-engineer42/joharnessburg (9 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 442 once invoked, about $0.0003 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.
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/.
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…
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.