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 skills add tranhieutt/software_development_department --skill using-sddgit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/using-sdd)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/using-sdd"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/using-sdd/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/using-sdd"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/using-sdd.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.02676 |
| Opus 5 | $0.00022 | $0.01338 |
| Sonnet 5 | $0.00009 | $0.00535 |
| Haiku 4.5 | $0.00004 | $0.00268 |
Grade A, and why
using-sdd 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 8d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using SDD
using-sdd is the router and discipline layer for the Software Development
Department. It does not replace specialist skills. It decides which SDD workflow
must govern the current request before the agent acts.
For phase orientation, use docs/technical/SDD_LIFECYCLE_MAP.md
(DEFINE -> PLAN -> BUILD -> VERIFY -> REVIEW -> SHIP). For detailed runtime
stage rules, use docs/technical/CONTROL_PLANE_MAP.md.
Core Rule
Before answering, asking clarifying questions, editing files, spawning agents, or claiming completion, check whether an SDD skill applies.
If a skill applies, use it. Do not rely on memory of the skill. Read the current skill and follow its gates.
Skill Routing
| User intent or situation | Required SDD workflow |
|---|---|
| Codex environment, Codex setup, AGENTS.md, .codex, Claude-to-Codex tool mapping, or SDD outside Claude Code | codex-sdd then route through using-sdd |
| First session, unclear project state | start |
| Vague product idea, ideation, product direction | brainstorm |
| User wants structured requirements or says "ask me", "don't assume", "interview" | deep-interview |
| New feature, behavior change, architectural change | spec-driven-development |
| Existing spec needs readiness review before planning or implementation | review-spec |
| Approved spec conflicts with code, tests, review findings, user feedback, or platform reality | spec-evolution |
| Framework, library, external API, platform behavior, deprecation, migration, or "latest/official/best practice" correctness matters | source-driven-development |
| Epic, multi-step work, large prompt, many files | planning-and-task-breakdown |
| Implementation of one approved task | test-driven-development |
| Execution of approved multi-task sequential plan with review gates | subagent-driven-development |
| Bug, failing test, build failure, CI failure, performance regression, or unexpected behavior | systematic-debugging |
| Complex, intermittent, unfamiliar, or repeatedly failed bug investigation | diagnose |
| Simple obvious bug with clear cause | test-driven-development with a regression test |
| Coordinated multi-agent work across domains | orchestrate |
| Independent parallel workstreams | fork-join |
| UI/frontend architecture or component design | frontend-design or ui-spec |
| API contract or endpoint design | api-design |
| Architecture decision with durable consequences | architecture-decision-records |
| Code quality, PR review, merge readiness | code-review or code-review-checklist |
| Prose quality for specs, ADRs, PR bodies, release notes, or technical docs | style-review |
| Behavior-preserving cleanup, simplification, readability refactor, or complexity reduction after tests pass | code-simplification |
| Review comments, PR feedback, CHANGES_REQUIRED verdict, or reviewer questions need response | receiving-code-review |
| Phase transition or readiness review | gate-check |
| Release or launch preparation | release-checklist or launch-checklist |
| Completion claim, success claim, task done, fixed, passing, ready, clean, merge-ready | verification-before-completion |
| Commit requested | commit |
| Create, update, refine, or evaluate an SDD skill; repeated prompt should become a skill; agent failure suggests missing/broken skill | learner |
| Save reusable lesson or preference | learner or annotate |
| Context is too large or stale | context-engineering or save-state |
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.
- 8d ago First seen · 257 lines · 43 tokens per session scan A b9a9d88efa38
using-sdd is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 2,676 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-09-03.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
tdd
Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.
verify
Fresh verification gate before claiming done, fixed, passing, ready, or before commit/PR. Evidence before claims, always.