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-applygit 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.04087 |
| Opus 5 | $0.00000 | $0.02044 |
| Sonnet 5 | $0.00000 | $0.00817 |
| Haiku 4.5 | $0.00000 | $0.00409 |
Grade A, and why
sdd-change-apply 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 — 764 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Change Apply Command
Apply a change proposal to the codebase.
Instructions for GitHub Copilot
You are executing the #sdd-change-apply [change-name] command to implement an approved change proposal.
Command Format
#sdd-change-apply add-2fa
#sdd-change-apply migrate-to-graphql
#sdd-change-apply refactor-auth-service
Your Task
Implement the changes defined in the change proposal, following constitutional governance and best practices.
Process
1. Read Change Proposal
IMPORTANT: Read the approved change proposal first:
# Read proposal
storage/changes/{{change-name}}-proposal.md
Extract:
- ADDED requirements
- MODIFIED requirements
- REMOVED requirements
- Implementation plan
- Testing requirements
- Success metrics
Verify Approval:
- Status must be "Approved" (not "Proposed" or "Rejected")
- If not approved, abort and notify user
2. Read Steering Context (Article VI)
# Read these files
steering/product.md # Product context
steering/structure.md # Architecture patterns
steering/tech.md # Technology stack
3. Set Up Feature Flag
Create Feature Flag (for gradual rollout):
// lib/feature-flags/flags.ts
export const FEATURE_FLAGS = {
// ... existing flags ...
enable_{{feature}}: {
enabled: false, // Start disabled
description: '{{CHANGE_DESCRIPTION}}',
rolloutPercentage: 0,
},
} as const;
Update Configuration:
// lib/feature-flags/config.ts
export function isFeatureEnabled(flag: keyof typeof FEATURE_FLAGS): boolean {
if (process.env.NODE_ENV === 'test') {
return true; // Always enabled in tests
}
const config = FEATURE_FLAGS[flag];
if (!config.enabled) return false;
// Gradual rollout logic
return Math.random() * 100 < config.rolloutPercentage;
}
4. Implement Changes (Library-First - Article I)
For Each ADDED Requirement:
Step 4.1: Create Library Module
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 · 764 lines · 0 tokens per session scan A fa3c6e23d29b
sdd-change-apply 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 4,087 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.