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 john-wilmes/claude-agentic-coding-playbook --skill create-projectgit clone --depth 1 https://github.com/john-wilmes/claude-agentic-coding-playbookWrote 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/john-wilmes/claude-agentic-coding-playbook/create-project)<a href="https://agentmods.dev/skills/john-wilmes/claude-agentic-coding-playbook/create-project"><img src="https://agentmods.dev/badge/skills/john-wilmes/claude-agentic-coding-playbook/create-project/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/john-wilmes/claude-agentic-coding-playbook/create-project"><img src="https://agentmods.dev/badge/skills/john-wilmes/claude-agentic-coding-playbook/create-project.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.00069 | $0.01358 |
| Opus 5.5 | $0.00028 | $0.00543 |
| Sonnet 5.5 | $0.00014 | $0.00272 |
| Haiku 4.5 | $0.00007 | $0.00136 |
Grade A, and why
create-project 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 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.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Project
Scaffold a new project following all global CLAUDE.md conventions.
Input
$ARGUMENTS= project name (required, kebab-case)
If no arguments provided, ask the user for a project name.
Steps
1. Determine install root
Run the install-root discovery helper:
INSTALL_ROOT=$(bash ~/.claude/scripts/skills/find-install-root.sh)
2. Gather requirements
Ask the user (single AskUserQuestion call):
- Project type: Node/TypeScript, Python, static site, or other
- Description: one-line summary for package.json and GitHub
3. Create directory
<INSTALL_ROOT>/<project-name>/
Fail if directory already exists.
4. Initialize git
cd <INSTALL_ROOT>/<project-name> && git init
5. Create .gitignore
Minimum entries per global CLAUDE.md Repository Hygiene rules:
node_modules/,dist/,.env*,*.log,.DS_Store,Thumbs.db
Add language-specific entries based on project type (e.g., __pycache__/ for Python, .next/ for Next.js).
6. Create project CLAUDE.md
Read the template at <INSTALL_ROOT>/.claude/templates/project-CLAUDE.md if available, otherwise use the built-in template.
Must include:
- Project name and one-line description
- Quality gate commands (type-check, lint, test) appropriate to the project type
- Language and framework conventions
- Architecture notes section (even if initially empty)
- Build and dependency instructions
7. Create AGENTS.md
Generate an AGENTS.md file at the project root. This is a cross-tool convention (60k+ repos) that tells any AI coding assistant how to build, test, and lint the project.
Populate sections from the quality gate commands chosen in step 6:
# AGENTS.md
## Build
<build command from quality gates, or "No build step configured.">
## Test
<test command from quality gates, e.g. "npm test">
## Lint
<lint command from quality gates, e.g. "npx eslint .">
## General
- Follow existing code style and naming conventions.
- Write tests for new functionality.
- Do not commit credentials or secrets.
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 · 170 lines · 69 tokens per session scan A e3039f702922
create-project is a skill published in the GitHub repository john-wilmes/claude-agentic-coding-playbook (4 stars, last pushed 6mo ago), licensed MIT. It adds 69 tokens to every session and 1,358 once invoked, about $0.0003 per session on Opus 5.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
ijfw-ship
Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.
feature
Full per-feature pipeline: implement → testloop → evaluator challenge → coder feedback → document → commit.
fix-issue
Resolve a GitHub issue end to end, from reading the issue through to opening a pull request. Use when the user names an issue number to fix.
papi-build
Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.
papi-auto
Continue an approved PAPI cycle through implementation, verification and review using bounded autonomy. Resume durable work without rebuilding it; propose new scope before persisting it.