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/drobins25/craft/craft-projectgit clone --depth 1 https://github.com/drobins25/craftWrote 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/drobins25/craft/craft-project)<a href="https://agentmods.dev/commands/drobins25/craft/craft-project"><img src="https://agentmods.dev/badge/commands/drobins25/craft/craft-project.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.00018 | $0.00598 |
| Opus 5 | $0.00009 | $0.00299 |
| Sonnet 5 | $0.00004 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft Project
Manage which project is active in a multi-project monorepo.
Behavior
No arguments: Show dashboard
Run the discover-projects.sh script to list all projects:
bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/discover-projects.sh"
This returns name|path|status|package_manager lines.
Display a dashboard like:
┌──────────────────────────────────────────────────────┐
│ PROJECTS │
├──────────────┬──────────┬───────────┬────────────────┤
│ Project │ Cycle │ Progress │ Status │
├──────────────┼──────────┼───────────┼────────────────┤
│ ● craftsman │ 7-ext │ 4/5 done │ active-dev │
│ ○ you-coded │ — │ — │ pre-dev │
│ ○ master │ — │ — │ planning │
└──────────────┴──────────┴───────────┴────────────────┘
Currently pinned: craftsman
For each project, read its .craft/.global-state to get ACTIVE_CYCLE, then read cycle state for progress. Mark the currently pinned project (from $CRAFT_PROJECT_ROOT env var) with a bullet.
With project name argument: Switch project
When the user provides a project name (e.g., /craft:project craftsman):
- Validate the project exists in the registry (or is "root"/"master" for the monorepo root)
- Resolve its absolute path
- Update the session env via
$CLAUDE_ENV_FILE:echo "export CRAFT_PROJECT_ROOT=\"/absolute/path/to/project\"" >> "$CLAUDE_ENV_FILE" echo "export CRAFT_PROJECT_NAME=\"craftsman\"" >> "$CLAUDE_ENV_FILE" - Write the persistent pin file (so hooks can resolve without env vars):
repo_root=$(git rev-parse --show-toplevel 2>/dev/null) printf '%s\n%s\n' "/absolute/path/to/project" "project-name" > "$repo_root/.craft/.pinned-project" - Show a mini status summary for the new project (backlog count, active cycle, etc.)
Important
- This command only applies to monorepo setups with multiple
.craft/directories - In single-project repos, inform the user there's only one project and no switching needed
- The project registry lives at the git repo root:
.craft/projects/*.md - Each registry file has YAML frontmatter with
name,path,status,package_manager
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.
- 4d ago First seen · 63 lines · 18 tokens per session scan A 5b664e092c02
project is a command published in the GitHub repository drobins25/craft (53 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 598 once invoked, about $0.0001 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-30.
Other commands, from other repositories
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
project
Manage projects inside a topic wiki. Projects are folders under output/projects/ that group related outputs (playbooks, images, code, data) with a goal captured in WHY.md.
luda
Invoke Luda, your Scrum Master, for board integrity — orphan work items, plan-vs-tracker divergence, Done-without-negative-criteria, parked-without-a-trigger — plus ticket creation and team orchestration.
task-conductor.skeleton
/task-conductor top 5 -> /task-conductor plan top 5 /task-conductor all -> /task-conductor plan all /task-conductor 3,5,8 -> /task-conductor plan 3,5,8 /task-conductor keyword auth -> /task-conductor plan keyword auth.