Borrowing it
Nothing to install: this file belongs to phuoctrung-ppt/ai-sdlc-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/phuoctrung-ppt/ai-sdlc-workflow/master/.cursor/commands/dev-module.mdgit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflowWrote 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/commands/phuoctrung-ppt/ai-sdlc-workflow/dev-module)<a href="https://agentmods.dev/commands/phuoctrung-ppt/ai-sdlc-workflow/dev-module"><img src="https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/dev-module/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/commands/phuoctrung-ppt/ai-sdlc-workflow/dev-module"><img src="https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/dev-module.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.00026 | $0.00704 |
| Opus 5.5 | $0.00010 | $0.00282 |
| Sonnet 5.5 | $0.00005 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
dev-module 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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Module Development Loop
Act as Orchestrator for module: {feature_name}
If
PLAN_APPROVEDexists for this module → skip Phase 1–2.
Context hygiene
Do not open into context:
.cursor/state/workflow-state.json(use CLI below for learning counter only).cursor/state/module-*-loop.json.aisdlc/*
Resume from docs/plans/, docs/module-deps.md, docs/memory/*.
Learning counter (write-only side effect, stdout is one compact JSON line):
python3 .cursor/scripts/learning-counter.py get
python3 .cursor/scripts/learning-counter.py inc --module {feature_name}
Office UI (when .aisdlc/ exists):
python3 .cursor/scripts/office-event.py --agent <id> --status working|done|idle|waiting|error --task "…" --phase <phase> --workflow {feature_name}
Phase 0 — Orient
cat docs/memory/decisions.md docs/memory/gotchas.md docs/memory/shortcuts.md 2>/dev/null || true
cat docs/module-deps.md 2>/dev/null || true
python3 .cursor/scripts/office-event.py --agent architect-planner --status working --task "Orient {feature_name}" --phase restore --workflow {feature_name}
Phases 1–5
Same as before: brainstorm → plan → scaffold → execute → test → judge/fix.
Emit office-event.py on each phase enter/exit. Use context-builder.py per agent.
Hard-gate execute on docs/module-deps.md.
Phase 6 — Done + Memory + Learning counter
- Append
docs/retrospective.md - Facts →
docs/memory/*(1–5) docs/module-deps.md→ moduledone- Increment counter (do not edit state JSON by hand):
python3 .cursor/scripts/learning-counter.py inc --module {feature_name}
# stdout e.g. {"modulesSinceLastProposal": 3, "fullPassRecommended": false}
- Dispatch
@learning-agent:- If stdout
fullPassRecommended: true→ task text includesfull pass - Else → lightweight scan
- If stdout
python3 .cursor/scripts/office-event.py --agent learning-agent --status working --task "Skill scan after {feature_name}" --phase review --workflow {feature_name}
python3 .cursor/context/context-builder.py \
--phase review \
--task "post-module skill scan for {feature_name}" \
--agent learning-agent \
--keywords "retrospective,pattern,skill,learning,gotcha,shortcut" \
--budget 5000
python3 .cursor/scripts/office-event.py --agent learning-agent --status done --task "Learning finished" --phase review --workflow {feature_name}
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.
- 1mo ago First seen · 85 lines · 26 tokens per session scan A 24e46cf6544a
dev-module is a command published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 704 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.