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/whchoi98/project-init/deploygit clone --depth 1 https://github.com/whchoi98/project-initWhat 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.00008 | $0.01004 |
| Opus 5 | $0.00004 | $0.00502 |
| Sonnet 5 | $0.00002 | $0.00201 |
| Haiku 4.5 | $0.00001 | $0.00100 |
Grade A, and why
deploy 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 yesterday.
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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy
Build and publish the project-init plugin.
Step 1: Pre-Deploy Checks
- Verify working tree is clean:
git status - Verify current branch (warn if not main):
git branch --show-current - Run
/test-allto validate plugin structure - Check if a deployment runbook exists:
ls docs/runbooks/deploy-*.md
Step 2: Version Validation
Both version files MUST match. Read and compare:
python3 -c "
import json
m = json.load(open('.claude-plugin/marketplace.json'))
p = json.load(open('plugins/project-init/.claude-plugin/plugin.json'))
mv = m['metadata']['version']
pv = p['version']
print(f'marketplace.json: {mv}')
print(f'plugin.json: {pv}')
if mv != pv:
print(f'ERROR: Version mismatch! Fix before deploying.')
exit(1)
print('Versions match.')
"
If versions don't match, update both files to the same version before proceeding.
Step 3: Changelog Verification
- Read
CHANGELOG.md - Verify the current version has an entry with today's date
- If missing, ask the user to update CHANGELOG.md before deploying
Step 4: Tag and Push
# Get current version
VERSION=$(python3 -c "import json; print(json.load(open('plugins/project-init/.claude-plugin/plugin.json'))['version'])")
# Check if tag already exists
git tag -l "v$VERSION"
# If tag doesn't exist, create it
git tag -a "v$VERSION" -m "Release v$VERSION"
# Push code and tags
git push origin main
git push origin "v$VERSION"
Step 5: User Update Instructions
After pushing, display:
## Release v<VERSION> Published
### For existing users:
claude plugin marketplace update project-init
claude plugin install project-init@project-init
# Restart Claude Code session
### For new users:
git clone https://github.com/whchoi98/project-init.git
claude plugin marketplace add ./project-init
claude plugin install project-init
Error Recovery
If version validation fails (Step 2)
Update both files to the same version:
# Edit both files to matching version, then:
git add .claude-plugin/marketplace.json plugins/project-init/.claude-plugin/plugin.json
git commit -m "fix: sync marketplace and plugin versions to X.Y.Z"
Restart from Step 2.
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.
- yesterday First seen · 141 lines · 8 tokens per session scan A f7513b18b81a
deploy is a command published in the GitHub repository whchoi98/project-init (2 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 1,004 once invoked, about $0.0000 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.