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/benkapner/claude-code-basecamp/diff-explaingit clone --depth 1 https://github.com/Benkapner/claude-code-basecampWhat 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.00033 | $0.00846 |
| Opus 5 | $0.00016 | $0.00423 |
| Sonnet 5 | $0.00007 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
diff-explain 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diff Explain Command
Explain code changes in plain language — what was done and why.
Instructions
Step 1: Get the Diff
Determine what to explain based on arguments:
- No arguments: explain uncommitted changes (
git diff+git diff --staged) - Branch name: explain difference from that branch (
git diff main...HEAD) - Commit range: explain those commits (
git log --oneline <range>) - MR/PR number: fetch and explain that MR
# Default: uncommitted changes
git diff --stat
git diff
# Or: branch comparison
git log --oneline main..HEAD
git diff main...HEAD --stat
Step 2: Analyze and Explain
For each logical group of changes, explain:
- What changed — in plain language, not file names
- Why — the intent behind the change (infer from commit messages, code context, and patterns)
- Impact — what this means for the project (new capability, bug fix, refactor, etc.)
Step 3: Format the Explanation
CHANGES EXPLAINED
=================
SUMMARY:
[1-2 sentences capturing the overall intent of all changes]
CHANGE 1: [descriptive title]
What: [plain language description]
Why: [inferred intent]
Files: [list of affected files]
CHANGE 2: [descriptive title]
What: [plain language description]
Why: [inferred intent]
Files: [list of affected files]
...
OVERALL IMPACT:
- [What's new or different for users of this code]
- [Any breaking changes or things to be aware of]
- [What to test]
Examples
Input: /diff-explain
Output:
CHANGES EXPLAINED
=================
SUMMARY:
The monolithic epic analysis script was split into 3 independent
pipeline steps, and closed issues are now kept for context
instead of being discarded.
CHANGE 1: Split summarize_epics.py into 3 scripts
What: The script that grouped issues, analyzed epics, and filtered
tasks was split into group_issues.py (grouping only),
summarize_epics.py (epic analysis only), and
filter_standalone_tasks.py (task filtering only).
Why: Each step can now be run and debugged independently.
Skipping one step doesn't require skipping the others.
Files: scripts/group_issues.py (new), scripts/summarize_epics.py,
scripts/filter_standalone_tasks.py (new), main.py
CHANGE 2: Keep closed issues as lightweight entries
What: Previously, 66% of fetched records were discarded because
they were closed. Now they're kept with just title, assignee,
and dates — no description or comments.
Why: The AI can now see the full picture of what was accomplished
vs what's still in progress, giving richer executive reports.
Files: scripts/fetch_data.py, prompts/epic_prompts.py,
prompts/category_prompts.py
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 · 113 lines · 33 tokens per session scan A a5a844c3a72a
diff-explain is a command published in the GitHub repository Benkapner/claude-code-basecamp (16 stars, last pushed 12d ago), licensed MIT. It adds 33 tokens to every session and 846 once invoked, about $0.0002 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-30.
Other commands, from other repositories
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.
propagate
Use after editing an upstream doc (PRD/SRS/tech-design/feature-spec) to propagate changes downstream and keep the entire doc chain consistent.
review
Use when reviewing spec-forge generated documents for quality, completeness, and consistency — auto-fixes issues if found.
analyze
Use when analyzing a document collection to map themes, find conflicts, gaps, and redundancies — generates landscape analysis report.
audit
Use when auditing existing project docs for quality, completeness, and code alignment — generates findings report with fix recommendations.
test-cases
Use when writing test cases, generating tests, supplementing test coverage, or improving test completeness — auto-scans project, designs multi-dimensional test cases with coverage matrix.