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 skills/data-wise/craft/modesnpx skills add Data-Wise/craft --skill modesgit clone --depth 1 https://github.com/Data-Wise/craftWhat 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.00059 | $0.01125 |
| Opus 5 | $0.00030 | $0.00562 |
| Sonnet 5 | $0.00012 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
mode-controller 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mode Controller Skill
Expert in managing craft plugin execution modes for different use cases.
Mode Definitions
| Mode | Time Budget | Use Case | Behavior |
|---|---|---|---|
| default | < 10s | Quick tasks | Minimal output, fast |
| debug | < 120s | Problem solving | Verbose, traces, detailed |
| optimize | < 180s | Performance | Profiling, benchmarks |
| release | < 300s | Pre-release | Thorough, comprehensive |
When to Use Each Mode
Default Mode
- Quick code checks
- Simple lookups
- Status queries
- Day-to-day operations
Debug Mode
- Investigating errors
- Tracing execution
- Understanding behavior
- Finding root causes
Optimize Mode
- Performance profiling
- Identifying bottlenecks
- Memory analysis
- Speed improvements
Release Mode
- Pre-deployment validation
- Complete test suites
- Documentation checks
- Full audits
Mode Selection Logic
If user specifies mode → use that mode
Else if error/bug context → debug mode
Else if performance context → optimize mode
Else if release/deploy context → release mode
Else → default mode
Mode-Specific Behaviors
Code Commands
| Command | Default | Debug | Optimize | Release |
|---|---|---|---|---|
| lint | Quick check | All rules + fix suggestions | Perf rules | All rules + strict |
| coverage | Summary | Line-by-line | Branch analysis | Full report |
| deps-check | Version only | Dependency tree | Size analysis | Security + licenses |
| ci-local | Fast checks | Full trace | Parallel jobs | All CI steps |
Test Commands
| Command | Default | Debug | Optimize | Release |
|---|---|---|---|---|
| run | Quick tests | Verbose + traces | Parallel | Full suite |
| coverage | Summary % | Uncovered lines | Branch % | HTML report |
| debug | Quick trace | Full stack trace | Profiling | All info |
Architecture Commands
| Command | Default | Debug | Optimize | Release |
|---|---|---|---|---|
| analyze | Overview | Deep dive | Hotspots | Full audit |
| review | Quick check | Line-by-line | Perf review | Comprehensive |
| diagram | Simple | Detailed | Data flow | Complete |
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 · 163 lines · 59 tokens per session scan A 8dee79d766f2
mode-controller is a skill published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It adds 59 tokens to every session and 1,125 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
github-actions-workflow
Scaffolds or audits a GitHub Actions CI/CD workflow for a project. Covers job structure, caching, secrets handling, concurrency groups, environment gates, and reusable workflows via workflowcall. Invoked when the user asks to set up CI, add a GitHub Actions workflow, improve pipeline performance, or share workflow…
specflow
Spec-driven development with executable contracts.
specflow-loop-selector
Selects the correct Specflow loop and forces a concrete run contract before work starts. Use when an agent is asked to start Specflow work, build a ticket, create/refine a PRD, investigate an existing product, run Gate D, choose between spec-build and feature-build, or "go find out about" Specflow loops. Compatible…
specflow-simulate
Simulates end-to-end usage of a Specflow story across multiple personas and divergent routes to discover gaps, edge cases, and unhandled branches BEFORE the story is built — then proposes each finding as a concrete story addition (new REQ, negative-path AC, Gherkin branch, or journey step). This is the high-value…
specflow-audit
Audits a Specflow story/ticket for spec-compliance and surgically uplifts it — adding only the missing executable contract sections (SQL/RLS, TypeScript interfaces, invariant codes, Gherkin, acceptance criteria, Definition of Done, data-testid coverage) — then runs a pre-flight gate that refuses to mark the ticket…
architecture-review
Conducts a comprehensive multi-perspective architecture review using ALL architecture team members. Use when the user requests "Start architecture review", "Full architecture review", "Review architecture for version X.Y.Z", "Conduct comprehensive review", or when they want assessment from multiple perspectives. Do…