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/drag88/claude-dev-framework/gitgit clone --depth 1 https://github.com/drag88/claude-dev-frameworkWhat 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.00009 | $0.00657 |
| Opus 5 | $0.00005 | $0.00329 |
| Sonnet 5 | $0.00002 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
git 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cdf:git - Git Operations
Triggers
- Git repository operations: status, add, commit, push, pull, branch
- Need for intelligent commit message generation
- Repository workflow optimization requests
- Branch management and merge operations
Usage
/cdf:git [operation] [args] [--interactive]
Behavioral Flow
- Analyze: Check repository state and working directory changes
- Route: Commit operations delegate to
compound-engineering:ce-commit; status, branch, merge, and other non-commit operations stay native. - Validate: Ensure operation is appropriate for current Git context
- Execute: Run the native Git operation or delegated commit flow
- Report: Provide status and next steps guidance
Key behaviors:
- Commit operations require the compound-engineering plugin and the
compound-engineering:ce-commithost skill - Apply consistent branch naming conventions
- Handle merge conflicts with guided resolution
- Provide clear status summaries and workflow recommendations
Delegation: compound-engineering
Commit operations delegate to the compound-engineering:ce-commit host skill.
Requires: the compound-engineering plugin. If it is not installed, stop and tell the user to install the compound-engineering plugin for their host (install commands are in the README) — do not improvise a replacement flow.
Flow: Invoke the compound-engineering:ce-commit host skill, passing the user's arguments, selected files, and any flags as context.
CDF constraints (bind on top of the skill):
- Use conventional commit format.
- Do not include AI attribution of any kind.
- Keep non-commit git operations native to this command.
Commit Message Rules
No Claude Attribution
Do NOT include Claude attribution in commits:
# BAD - Don't include this:
Co-Authored-By: Claude <[email protected]>
Conventional Format
Follow conventional commit format:
feat:- new featurefix:- bug fixdocs:- documentationrefactor:- code refactoringtest:- adding testschore:- maintenance
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 · 94 lines · 9 tokens per session scan A 55265a094531
git is a command published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 657 once invoked, about $0.0000 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 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.