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-cycle-completegit 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-cycle-complete)<a href="https://agentmods.dev/commands/drobins25/craft/craft-cycle-complete"><img src="https://agentmods.dev/badge/commands/drobins25/craft/craft-cycle-complete.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.00019 | $0.03497 |
| Opus 5 | $0.00010 | $0.01749 |
| Sonnet 5 | $0.00004 | $0.00699 |
| Haiku 4.5 | $0.00002 | $0.00350 |
Grade A, and why
cycle-complete 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.
How it starts
The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cycle Complete
Complete and archive a cycle. Ensures learnings are reflected before archiving.
When to Use
- All stories in the cycle are complete
- User explicitly ends cycle early
- Cycle has been abandoned and needs archival
Flow
Step 1: Verify Cycle State
Set cycle_dir to .craft/cycles/${ACTIVE_CYCLE}.
Use Grep with pattern ^status: complete, path $cycle_dir/stories/, glob *.md, output_mode files_with_matches → count results → stories_complete.
Use Glob with pattern $cycle_dir/stories/*.md → count results → stories_total.
If stories incomplete: Use AskUserQuestion:
question: "[N] of [M] stories complete. End cycle anyway?"
header: "Cycle"
options:
- label: "Complete cycle"
description: "Archive incomplete stories to backlog"
- label: "Continue working"
description: "Finish remaining stories first"
Step 2: Check for Pending Learnings & Ungraduated Fixes
Use Grep with pattern status: pending, path .craft/.learnings.yaml, output_mode count → pending_count. If file doesn't exist, pending_count = 0.
Also count ungraduated fix records and the rule-pass threshold:
FIX_COUNT=$(bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/count-ungraduated-fixes.sh")
THRESHOLD=$(grep -m1 '^rule_pass_threshold:' "${CRAFT_PROJECT_ROOT:-.}/.craft/settings.yaml" 2>/dev/null | sed 's/^rule_pass_threshold:[[:space:]]*//')
THRESHOLD=${THRESHOLD:-10}
If pending_count > 0 OR FIX_COUNT >= THRESHOLD:
Name the reason(s) that apply:
"There are [N] pending learnings that haven't been converted to harness yet." "[FIX_COUNT] fixes have accumulated since the last rule pass - reflect can mine them for graduation-worthy rules."
"Reflect before archiving?"
Use AskUserQuestion:
question: "Reflect before archiving?"
header: "Reflect"
options:
- label: "Yes, reflect now"
description: "Run /craft:reflect (learnings drain and/or rule pass), then archive"
- label: "Skip reflection"
description: "Keep everything pending, just archive cycle"
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 · 404 lines · 19 tokens per session scan A de3c757066a5
cycle-complete is a command published in the GitHub repository drobins25/craft (53 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 3,497 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
claudehut-learning-report
Show the ClaudeHut learning scoreboard — measured memory health (store size, reinforcement, effectiveness/recurrence, quality) so you can tell whether the agent is actually getting smarter across sessions. One-shot, read-only.
orchestrate
This tool coordinates Claude Code's actions. It does NOT write code or create content.
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
performance-bottlenecks
Identify and resolve performance bottlenecks in your development workflow.