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/nahisaho/codegraphmcpserver/sdd-change-archivegit clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServerWhat 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.03495 |
| Opus 5 | $0.00000 | $0.01747 |
| Sonnet 5 | $0.00000 | $0.00699 |
| Haiku 4.5 | $0.00000 | $0.00349 |
Grade C, and why
sdd-change-archive scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf lib/{{deprecated-feature}}/ How it starts
The opening of the file, as written. The whole thing — 686 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Change Archive Command
Archive a completed change proposal.
Instructions for GitHub Copilot
You are executing the #sdd-change-archive [change-name] command to archive a completed change.
Command Format
#sdd-change-archive add-2fa
#sdd-change-archive migrate-to-graphql
#sdd-change-archive refactor-auth-service
Your Task
Archive the change proposal and implementation, update documentation, and clean up temporary resources.
Process
1. Verify Change Completion
Read Implementation Report:
# Check implementation report exists
storage/changes/{{change-name}}-implementation.md
Verify Status:
- Implementation report exists
- All requirements implemented
- Tests passing
- Feature deployed to production
- Feature flag enabled (or deprecated feature removed)
- Monitoring shows stable metrics
If Not Complete:
⚠️ **Change not ready for archival**
Status Check:
- [ ] Implementation complete
- [ ] Tests passing
- [ ] Deployed to production
- [ ] Feature flag enabled/removed
- [ ] Stable for 2+ weeks
Please complete all steps before archiving.
2. Collect Final Metrics
Gather Success Metrics:
## Final Metrics: {{CHANGE_NAME}}
### Deployment
- **Deployed**: {{DATE}}
- **Rollout Complete**: {{DATE}}
- **Stable Period**: {{DAYS}} days
### Performance
- **P95 Latency**: {{VALUE}}ms (target: <200ms) ✅
- **Error Rate**: {{VALUE}}% (target: <0.1%) ✅
- **Throughput**: {{VALUE}} req/s ✅
### Adoption
- **User Adoption**: {{PERCENTAGE}}%
- **Feature Usage**: {{COUNT}} uses/day
- **Customer Feedback**: NPS {{SCORE}}
### Quality
- **Bugs Found**: {{COUNT}}
- P0: 0
- P1: {{COUNT}}
- P2: {{COUNT}}
- **Incidents**: {{COUNT}}
- **Rollbacks**: {{COUNT}}
### Cost
- **Development Time**: {{HOURS}} hours
- **Infrastructure Cost**: ${{AMOUNT}}/month
- **ROI**: {{PERCENTAGE}}% (projected)
3. Update Change Status
Update Change Proposal:
<!-- storage/changes/{{change-name}}-proposal.md -->
## Metadata
- **Change ID**: CHG-{{NUMBER}}
- **Status**: ~~Proposed~~ → ~~Approved~~ → ~~Implemented~~ → **Archived**
- **Created**: {{DATE}}
- **Approved**: {{DATE}}
- **Implemented**: {{DATE}}
- **Archived**: {{DATE}}
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.
- 2d ago First seen · 686 lines · 0 tokens per session scan C d68789c9b51d
sdd-change-archive is a command published in the GitHub repository nahisaho/CodeGraphMCPServer (12 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,495 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.