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-list)<a href="https://agentmods.dev/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-list"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-list/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-list"><img src="https://agentmods.dev/badge/commands/stanleykao72/claude-code-spec-workflow-odoo/odoo-spec-list.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.00962 |
| Opus 5 | $0.00000 | $0.00481 |
| Sonnet 5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
odoo-spec-list 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-spec-list - List All Odoo Module Specifications
List all specifications across all Odoo modules in the project, including features, bugs, and module tests.
Usage
/odoo-spec-list
What This Command Does
This command scans all detected Odoo modules and lists their specifications, providing a comprehensive overview of development work across the entire Odoo project.
Instructions
Use the @odoo-spec-task-executor agent to list Odoo module specifications:
Scan and list all Odoo module specifications across the entire project:
# 1. Module Discovery
- Detect all Odoo modules in the project using odoo-detect functionality
- Look for modules in standard paths (custom_addons/, addons/, modules/)
- Include both auto-detected and manually configured modules
# 2. Specification Scanning
For each discovered module, scan the .spec/ directory structure:
## Features (.spec/features/[feature-name]/)
- request.md: Feature request and justification
- requirements.md: Business requirements
- design.md: Technical design
- tasks.md: Implementation tasks
## Bug Fixes (.spec/bugs/[bug-name]/)
- report.md: Bug report and analysis
- analysis.md: Root cause analysis
- fix.md: Implementation details
- verification.md: Testing strategy
## Module Tests (.spec/testing/)
- testing-plan.md: Testing strategy
- test-cases.md: Test specifications
- test-implementation.md: Test code
- performance-tests.md: Performance benchmarks
- ci-cd-integration.md: CI/CD guides
# 3. Output Format
Display comprehensive module-wise specification overview:
📋 Odoo Project Specifications Overview
📊 Project Summary: • Total Modules: X • Total Features: X • Total Bug Fixes: X • Total Tests: X
🏗️ MODULE: [module-name] (Path: [module-path]) ├── 🚀 Features (X): │ ├── feature-1 (Complete) - Last updated: YYYY-MM-DD │ │ └── Phase: Implementation (7/8 tasks) │ ├── feature-2 (In Progress) - Last updated: YYYY-MM-DD │ │ └── Phase: Design │ └── feature-3 (Planning) - Last updated: YYYY-MM-DD │ └── Phase: Requirements │ ├── 🐛 Bug Fixes (X): │ ├── bug-1 (Fixed) - Last updated: YYYY-MM-DD │ │ └── Status: Verified │ └── bug-2 (In Progress) - Last updated: YYYY-MM-DD │ └── Status: Analysis │ └── 🧪 Tests (X): ├── unit-tests (Complete) - Last updated: YYYY-MM-DD │ └── Coverage: 85% └── integration-tests (In Progress) - Last updated: YYYY-MM-DD └── Coverage: 60%
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 · 125 lines · 0 tokens per session scan A 8a2ef77c4a84
odoo-spec-list 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 962 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.