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/odoo-spec-status)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-status"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-status/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/odoo-spec-status"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-status.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.01708 |
| Opus 5 | $0.00000 | $0.00854 |
| Sonnet 5 | $0.00000 | $0.00342 |
| Haiku 4.5 | $0.00000 | $0.00171 |
Grade A, and why
odoo-spec-status 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 9d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-spec-status - Show Detailed Odoo Module Specification Status
Show detailed status of Odoo module specifications, including features, bugs, and tests.
Usage
/odoo-spec-status [module-name] [spec-type] [spec-name]
Parameters:
module-name(optional): Specific module to checkspec-type(optional): Type of spec (features, bugs, testing)spec-name(optional): Specific specification name
Examples:
/odoo-spec-status # All modules status
/odoo-spec-status inventory_custom # Specific module status
/odoo-spec-status inventory_custom features # Module features only
/odoo-spec-status inventory_custom features stock-enhancement # Specific feature
What This Command Does
This command provides detailed status information for Odoo module specifications, showing progress, completion status, and next recommended actions.
Instructions
Use the @odoo-spec-task-executor agent to show Odoo specification status:
Display detailed Odoo specification status with module-aware analysis:
# 1. Parameter Processing
Determine scope based on provided parameters:
## No parameters: Project-wide status
- Show summary for all modules
- Highlight modules with active development
- Display overall project health metrics
## Module-name only: Module-specific status
- Show all specifications within the specified module
- Include module metadata and dependencies
- Display module development progress
## Module + spec-type: Type-specific status
- Show only features, bugs, or testing specifications
- Include type-specific metrics and recommendations
## Full specification: Detailed spec status
- Show complete workflow status for specific specification
- Include task-level progress and next actions
# 2. Status Analysis Framework
For each specification found, analyze:
## File Presence Check
- ✅ All required files exist
- ⚠️ Some files missing
- ❌ Critical files missing
## Content Completeness Check
- Analyze file content quality and completeness
- Check for placeholder text or incomplete sections
- Validate against Odoo-specific requirements
## Timestamp Analysis
- Show last modification dates
- Identify stale or outdated specifications
- Highlight recent activity
# 3. Detailed Output Format
## Project-Wide Status (no parameters)
📊 Odoo Project Development Status
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.
- 9d ago First seen · 232 lines · 0 tokens per session scan A 604d586f9260
odoo-spec-status 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 1,708 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.