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/tranhieutt/software_development_department/codex-sddnpx skills add tranhieutt/software_development_department --skill codex-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/codex-sdd)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/codex-sdd"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/codex-sdd.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.00051 | $0.01008 |
| Opus 5 | $0.00026 | $0.00504 |
| Sonnet 5 | $0.00010 | $0.00202 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
codex-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 6d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex SDD
codex-sdd is the Codex adapter for the Software Development Department.
It does not replace Claude Code behavior. It helps Codex follow the existing SDD contract without changing the Claude-native runtime.
Core Rule
Treat these files as the SDD source of truth:
CLAUDE.md.claude/skills/using-sdd/SKILL.mddocs/technical/SDD_LIFECYCLE_MAP.md.claude/settings.jsonfor Claude-only runtime behavior
Use using-sdd for routing. Use this skill only for Codex-specific adaptation.
Non-Impact Boundary
Do not change these for Codex-only reasons:
.claude/settings.json.claude/hooks/- existing skill names or directories
- existing agent names or files
- Claude workflow semantics for
/plan,/spec,/tdd,/context, or other SDD commands
Codex compatibility must be additive unless the user explicitly approves a broader Claude regression-tested change.
Codex Session Start
At the start of a Codex session in SDD:
- Read
AGENTS.md. - Read
.claude/skills/using-sdd/SKILL.md. - Use
docs/technical/SDD_LIFECYCLE_MAP.mdfor phase orientation. - Select the governing SDD skill for the user request.
- Remember that Claude hooks do not auto-run in Codex.
Tool Mapping
| Claude-style tool | Codex equivalent |
|---|---|
Read |
shell read commands or direct file inspection |
Glob |
rg --files or shell listing |
Grep |
rg |
Write |
apply_patch |
Edit |
apply_patch |
Bash |
shell_command |
RunCommand |
shell_command |
Task |
spawn_agent only when explicitly authorized |
TodoWrite |
update_plan |
AskUserQuestion |
concise direct user question |
WebSearch |
web search only when required or explicitly requested |
Manual Hook Equivalents
Claude Code hooks in .claude/settings.json do not run automatically in Codex.
Use manual equivalents:
| Claude behavior | Codex behavior |
|---|---|
| Session bootstrap | Read AGENTS.md, using-sdd, lifecycle map, and relevant memory. |
| Pre-code gate | State the SDD pre-code gate before edits. |
| Bash safety | Follow Codex sandbox and escalation rules. |
| File history | Use git log -- <file> when needed. |
| Write logging | Use git diff/status and final changed-file summary. |
| Circuit guard | Inspect .claude/memory/circuit-state.json before subagent workflows. |
| Completion gate | Use verification-before-completion before success claims. |
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.
- 6d ago First seen · 122 lines · 51 tokens per session scan A 00ebd0b704e5
codex-sdd is a skill published in the GitHub repository tranhieutt/software_development_department (71 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 1,008 once invoked, about $0.0003 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
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…
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).
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.
analyze
Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.
scan
Scan project once per session. Run first — all other skills depend on this.
tdd
Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.