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.
git clone --depth 1 https://github.com/RahSwe/claude-code-full-dev-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/rahswe/claude-code-full-dev-workflow/help)<a href="https://agentmods.dev/commands/rahswe/claude-code-full-dev-workflow/help"><img src="https://agentmods.dev/badge/commands/rahswe/claude-code-full-dev-workflow/help/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/rahswe/claude-code-full-dev-workflow/help"><img src="https://agentmods.dev/badge/commands/rahswe/claude-code-full-dev-workflow/help.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.00008 | $0.00708 |
| Opus 5.5 | $0.00003 | $0.00283 |
| Sonnet 5.5 | $0.00002 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
help 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Dev Workflow Plugin
A comprehensive feature development workflow with code mapping, TDD, multi-agent review, and PR management.
Commands
| Command | Description |
|---|---|
/full-dev-workflow:full-dev <feature> |
Start the full development workflow |
/full-dev-workflow:resume |
Resume an interrupted workflow |
/full-dev-workflow:help |
Show this help message |
Workflow Phases
| Phase | Name | Description |
|---|---|---|
| 0 | Plan Mode | Create feature specification and get user approval |
| 1 | Code Mapping | Explore codebase and identify affected files |
| 2 | Test Creation | Write E2E, integration, and unit tests (TDD) |
| 3 | Implementation (Tasks) | Parallel sub-agent execution with task groups until tests pass |
| 4 | Code Review | Multi-agent review (5 perspectives) |
| 5 | Auto Fixes | Automatically fix high-confidence issues |
| 6 | Code Simplification | Refactor for clarity and maintainability |
| 7 | UI Verification | Browser testing for UI features |
| 8 | Push PR | Create well-documented pull request |
| 9-10 | PR Review Loop | Address feedback until approval |
Bundled Agents
This plugin includes specialized agents for each phase:
full-dev-workflow:code-explorer- Phase 1 code mappingfull-dev-workflow:test-architect- Phase 2 test designfull-dev-workflow:reviewer-conventions- Phase 4 convention compliancefull-dev-workflow:reviewer-bugs- Phase 4 bug detectionfull-dev-workflow:reviewer-quality- Phase 4 code qualityfull-dev-workflow:reviewer-security- Phase 4 security reviewfull-dev-workflow:reviewer-performance- Phase 4 performance reviewfull-dev-workflow:code-simplifier- Phase 6 code simplification (uses Opus model)
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 · 79 lines · 8 tokens per session scan A 738c7273b8b8
help is a command published in the GitHub repository RahSwe/claude-code-full-dev-workflow (6 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 708 once invoked, about $0.0000 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.