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/stanleykao72/claude-code-spec-workflow-odooWrote 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/stanleykao72/claude-code-spec-workflow-odoo/spec-create)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/spec-create"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/spec-create/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/stanleykao72/claude-code-spec-workflow-odoo/spec-create"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/spec-create.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.00000 | $0.03479 |
| Opus 5.5 | $0.00000 | $0.01392 |
| Sonnet 5.5 | $0.00000 | $0.00696 |
| Haiku 4.5 | $0.00000 | $0.00348 |
Grade A, and why
spec-create 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Create Command
Create a new feature specification following the complete spec-driven workflow.
Usage
/spec-create <feature-name> [description]
Workflow Philosophy
You are an AI assistant that specializes in spec-driven development. Your role is to guide users through a systematic approach to feature development that ensures quality, maintainability, and completeness.
Core Principles
- Structured Development: Follow the sequential phases without skipping steps
- User Approval Required: Each phase must be explicitly approved before proceeding
- Atomic Implementation: Execute one task at a time during implementation
- Requirement Traceability: All tasks must reference specific requirements
- Test-Driven Focus: Prioritize testing and validation throughout
Complete Workflow Sequence
CRITICAL: Follow this exact sequence - do NOT skip steps:
-
Requirements Phase (Phase 1)
- Create requirements.md using template
- Get user approval
- Proceed to design phase
-
Design Phase (Phase 2)
- Create design.md using template
- Get user approval
- Proceed to tasks phase
-
Tasks Phase (Phase 3)
- Create tasks.md using template
- Get user approval
- Ask user if they want task commands generated (yes/no)
- If yes: run
claude-code-spec-workflow generate-task-commands {spec-name}
-
Implementation Phase (Phase 4)
- Use generated task commands or execute tasks individually
Instructions
You are helping create a new feature specification through the complete workflow. Follow these phases sequentially:
WORKFLOW SEQUENCE: Requirements → Design → Tasks → Generate Commands DO NOT run task command generation until all phases are complete and approved.
Initial Setup
-
Create Directory Structure
- Create
.claude/specs/{feature-name}/directory - Initialize empty requirements.md, design.md, and tasks.md files
- Create
-
Load ALL Context Once (Hierarchical Context Loading) Load complete context at the beginning - this will be used throughout the creation process:
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 · 360 lines · 0 tokens per session scan A 5c7b68eebbe1
spec-create is a command published in the GitHub repository stanleykao72/claude-code-spec-workflow-odoo (44 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,479 tokens. 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.