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-initgit 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.03533 |
| Opus 5 | $0.00000 | $0.01767 |
| Sonnet 5 | $0.00000 | $0.00707 |
| Haiku 4.5 | $0.00000 | $0.00353 |
Grade A, and why
sdd-change-init 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 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.
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 — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Change Init Command
Initialize a change proposal for brownfield projects.
Instructions for GitHub Copilot
You are executing the #sdd-change-init [change-name] command to create a change proposal for an existing codebase.
Command Format
#sdd-change-init add-2fa
#sdd-change-init migrate-to-graphql
#sdd-change-init refactor-auth-service
Your Task
Generate a change proposal specification that documents what will be added, modified, or removed in the existing system.
Process
1. Read Steering Context (Article VI)
IMPORTANT: Before starting, read steering files to understand current system:
# Read these files first
steering/product.md # Current product context
steering/structure.md # Existing architecture
steering/tech.md # Current technology stack
Extract:
- Current architecture patterns
- Existing components
- Technology stack
- Known constraints
2. Analyze Existing System
Research Current Implementation:
# Search for related code
grep -r "{{related-feature}}" src/
grep -r "{{related-feature}}" lib/
# Find existing requirements
ls storage/specs/*requirements.md
# Check existing design documents
ls storage/specs/*design.md
Document Current State:
- What exists now?
- What components are affected?
- What dependencies exist?
- What tests cover this area?
3. Gather Change Requirements
Methods:
A. Stakeholder Interview
Use AskUserQuestion tool to ask:
- Why is this change needed?
- What problem does it solve?
- What are the business drivers?
- What is the scope of the change?
- What must NOT change (backward compatibility)?
- What is the timeline/deadline?
B. Impact Analysis
Identify affected areas:
- Frontend components
- Backend services
- Database schema
- APIs (internal/external)
- Third-party integrations
- Tests
- Documentation
4. Create Change Proposal Document
Use template from templates/change-proposal.md:
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 · 646 lines · 0 tokens per session scan A 3351216f066f
sdd-change-init 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,533 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-30.
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.