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 commands/stanleykao72/claude-code-spec-workflow-odoo/spec-executegit 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-execute)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/spec-execute"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/spec-execute.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 | $0.00000 | $0.00963 |
| Opus 5 | $0.00000 | $0.00481 |
| Sonnet 5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
spec-execute 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 4d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Execute Command
Execute specific tasks from the approved task list.
Usage
/spec-execute [task-id] [feature-name]
Phase Overview
Your Role: Execute tasks systematically with validation
This is Phase 4 of the spec workflow. Your goal is to implement individual tasks from the approved task list, one at a time.
Instructions
Execution Steps:
Step 1: Load Context
# Load steering documents (if available)
claude-code-spec-workflow get-steering-context
# Load specification context
claude-code-spec-workflow get-spec-context {feature-name}
# Load specific task details
claude-code-spec-workflow get-tasks {feature-name} {task-id} --mode single
Step 2: Execute with Agent
Use the spec-task-executor agent:
Use the spec-task-executor agent to implement task {task-id} for the {feature-name} specification.
## Steering Context
[PASTE THE COMPLETE OUTPUT FROM get-steering-context COMMAND HERE]
## Specification Context
[PASTE THE REQUIREMENTS AND DESIGN SECTIONS FROM get-spec-context COMMAND HERE]
## Task Details
[PASTE THE OUTPUT FROM get-tasks SINGLE COMMAND HERE]
## Instructions
- Implement ONLY the specified task: {task-id}
- Follow all project conventions and leverage existing code
- Mark the task as complete using: claude-code-spec-workflow get-tasks {feature-name} {task-id} --mode complete
- Provide a completion summary
-
Task Execution
- Focus on ONE task at a time
- If task has sub-tasks, start with those
- Follow the implementation details from design.md
- Verify against requirements specified in the task
-
Implementation Guidelines
- Write clean, maintainable code
- Follow steering documents: Adhere to patterns in tech.md and conventions in structure.md
- Follow existing code patterns and conventions
- Include appropriate error handling
- Add unit tests where specified
- Document complex logic
-
Validation
- Verify implementation meets acceptance criteria
- Run tests if they exist
- Check for lint/type errors
- Ensure integration with existing code
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.
- 4d ago First seen · 134 lines · 0 tokens per session scan A 9ae65cc521fe
spec-execute 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 963 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.