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/data-wise/claude-plugins/codegit clone --depth 1 https://github.com/Data-Wise/claude-pluginsWhat 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.00000 | $0.00391 |
| Opus 5 | $0.00000 | $0.00196 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
code 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.
What it actually says
Code & Testing Commands
Development workflow tools with mode support - 17 commands.
Linting & Code Quality
/craft:code:lint
/craft:code:lint # default mode
/craft:code:lint debug # Verbose with suggestions
/craft:code:lint optimize # Fast parallel linting
Testing
/craft:test:run
/craft:test:run # default mode
/craft:test:run debug # Verbose test output
/craft:test:run release # Full suite with coverage
CI/CD Commands
/craft:code:ci-fix
Auto-fix common CI/CD issues (linting, formatting, missing files).
/craft:code:ci-local
Run CI checks locally before pushing.
Dependencies
/craft:code:deps-audit
Security audit of dependencies with vulnerability reports.
/craft:code:deps-check
Check for outdated dependencies and breaking changes.
Documentation Integration
/craft:code:docs-check
Validate code documentation is up-to-date with implementation.
Release Management
/craft:code:release
Complete release checklist (tests, docs, changelog, version bump).
Advanced Testing
/craft:test:cli-gen
Generate CLI test suites with comprehensive coverage.
/craft:test:cli-run
Run CLI-specific tests with output validation.
/craft:test:watch
Watch mode for continuous testing during development.
Other Commands
/craft:code:debug- Systematic debugging/craft:code:demo- Create demonstrations/craft:code:refactor- Refactoring guidance/craft:code:review- Code review assistance/craft:test:generate- Test generation/craft:test:strategy- Testing strategy
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 · 70 lines · 0 tokens per session scan A 9d3458ff0108
code is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 391 tokens. 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.