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 skills/yi-john-huang/sdd-mcp/sdd-commitnpx skills add yi-john-huang/sdd-mcp --skill sdd-commitgit clone --depth 1 https://github.com/yi-john-huang/sdd-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/yi-john-huang/sdd-mcp/sdd-commit)<a href="https://agentmods.dev/skills/yi-john-huang/sdd-mcp/sdd-commit"><img src="https://agentmods.dev/badge/skills/yi-john-huang/sdd-mcp/sdd-commit.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00038 | $0.01534 |
| Opus 5 | $0.00019 | $0.00767 |
| Sonnet 5 | $0.00008 | $0.00307 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
sdd-commit 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 5d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Commit & PR Guidelines
Create clear, consistent commit messages and pull requests that document changes effectively.
Commit Message Format
Follow the Conventional Commits specification:
<type>(<scope>): <subject>
[optional body]
[optional footer(s)]
Type Prefixes
| Type | When to Use | Example |
|---|---|---|
feat |
New feature | feat(auth): add JWT refresh token |
fix |
Bug fix | fix(api): handle null user response |
docs |
Documentation only | docs(readme): update installation steps |
style |
Formatting, no code change | style(lint): fix linter warnings |
refactor |
Code change, no new feature or fix | refactor(user): extract validation logic |
perf |
Performance improvement | perf(query): add index for user lookup |
test |
Adding/updating tests | test(auth): add login failure tests |
build |
Build system changes | build(deps): update dependencies |
ci |
CI/CD changes | ci(github): add test workflow |
chore |
Other changes | chore(deps): bump lodash version |
revert |
Revert previous commit | revert: feat(auth): add JWT refresh |
Scope
The scope should indicate the area affected:
feat(auth): # Authentication module
fix(api/users): # Users API endpoint
docs(readme): # README file
test(e2e): # End-to-end tests
refactor(db): # Database layer
Subject Line
- Use imperative mood: "add" not "added" or "adds"
- Don't capitalize first letter
- No period at the end
- Max 50 characters
# GOOD
feat(auth): add password reset flow
fix(cart): prevent duplicate items
# BAD
feat(auth): Added password reset flow.
fix(cart): Fixes the duplicate items bug
Body (Optional)
Use for explaining:
- What changed and why
- Breaking changes
- Related issues
feat(auth): add multi-factor authentication
Implement TOTP-based 2FA for enhanced security.
Users can now enable 2FA from their profile settings.
- Add TOTP secret generation
- Add QR code for authenticator apps
- Add backup codes for recovery
Closes #123
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.
- 5d ago First seen · 286 lines · 38 tokens per session scan A 3612aeb79ee6
sdd-commit is a skill published in the GitHub repository yi-john-huang/sdd-mcp (51 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,534 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…