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 Data-Wise/craft --skill modesgit clone --depth 1 https://github.com/Data-Wise/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/skills/data-wise/craft/modes)<a href="https://agentmods.dev/skills/data-wise/craft/modes"><img src="https://agentmods.dev/badge/skills/data-wise/craft/modes/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/data-wise/craft/modes"><img src="https://agentmods.dev/badge/skills/data-wise/craft/modes.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.00059 | $0.01125 |
| Opus 5.5 | $0.00024 | $0.00450 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 yesterday), licensed MIT. It adds 59 tokens to every session and 1,125 once invoked, about $0.0002 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
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
pdlc-ship
A software release workflow that runs tests, updates the version and change log, creates a Git tag, and starts CI/CD, the automated build and deployment process.
tfx-ship
A release workflow for publishing triflux versions through GitHub Releases, the npm package registry, and the Claude Code marketplace. It also supports version changes, dry runs, skipped tests, and no-publish runs.
bisect
Pinpoint the first bad commit for a reproducible regression in a safe temporary worktree. Use when HEAD is bad, a known revision is good, and one unattended command distinguishes them; handles flaky endpoints and git-bisect skip exit 125.