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.
git clone --depth 1 https://github.com/Data-Wise/claude-pluginsWrote 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/data-wise/claude-plugins/do)<a href="https://agentmods.dev/commands/data-wise/claude-plugins/do"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/do/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/commands/data-wise/claude-plugins/do"><img src="https://agentmods.dev/badge/commands/data-wise/claude-plugins/do.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.00009 | $0.01633 |
| Opus 5.5 | $0.00004 | $0.00653 |
| Sonnet 5.5 | $0.00002 | $0.00327 |
| Haiku 4.5 | $0.00001 | $0.00163 |
Grade A, and why
do 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/craft:do - Universal Command
Intelligently analyze your task and execute the right craft commands.
Usage
/craft:do <task description>
How It Works
- Check Spec - Look for existing spec matching task (NEW in v1.1.0)
- Analyze - Parse task description for intent
- Route - Select appropriate craft commands
- Execute - Run commands in optimal order
- Report - Summarize what was done
Examples
Feature Development
/craft:do add user authentication
# Routes to:
# 1. /craft:arch:plan - Design the feature
# 2. /craft:code:test-gen - Generate tests
# 3. /craft:git:branch - Create feature branch
Bug Fixing
/craft:do fix the login redirect issue
# Routes to:
# 1. /craft:code:debug - Analyze the issue
# 2. /craft:test:run - Run related tests
# 3. /craft:git:sync - Commit fix
Code Quality
/craft:do improve code quality
# Routes to:
# 1. /craft:code:lint - Check style
# 2. /craft:test:coverage - Check coverage
# 3. /craft:code:refactor - Suggest improvements
Documentation
/craft:do update documentation
# Routes to:
# 1. /craft:docs:sync - Sync docs with code
# 2. /craft:docs:validate - Check links
# 3. /craft:docs:changelog - Update changelog
Release Preparation
/craft:do prepare for release
# Routes to:
# 1. /craft:code:deps-audit - Security scan
# 2. /craft:test:run release - Full tests
# 3. /craft:code:lint release - Full lint
# 4. /craft:docs:changelog - Update changelog
# 5. /craft:code:release - Release workflow
Task Categories
| Category | Keywords | Commands Used |
|---|---|---|
| Feature | add, create, implement, build | arch:plan, code:test-gen, git:branch |
| Bug | fix, debug, issue, error | code:debug, test:run, test:debug |
| Quality | lint, quality, clean, improve | code:lint, test:coverage, code:refactor |
| Docs | document, update docs, readme | docs:sync, docs:validate, docs:changelog |
| Test | test, coverage, verify | test:run, test:coverage, test:debug |
| Release | release, deploy, publish | deps-audit, lint, test:run, code:release |
| Architecture | design, refactor, restructure | arch:analyze, arch:plan, arch:diagram |
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 · 222 lines · 9 tokens per session scan A afb011ece323
do is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 1,633 once invoked, about $0.0000 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 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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.