Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Viindoo/odoo-mcp-client/plugin install odoo-ai-agentsWrote 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/viindoo/odoo-mcp-client/odoo-position-feature)<a href="https://agentmods.dev/commands/viindoo/odoo-mcp-client/odoo-position-feature"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-position-feature/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/viindoo/odoo-mcp-client/odoo-position-feature"><img src="https://agentmods.dev/badge/commands/viindoo/odoo-mcp-client/odoo-position-feature.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.00062 | $0.00593 |
| Opus 5 | $0.00031 | $0.00296 |
| Sonnet 5 | $0.00012 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
odoo-position-feature 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 8d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/odoo-position-feature
Thin dispatcher - execution is fully encoded in the declarative workflow SSOT:
plugins/odoo-ai-agents/workflows/odoo-position-feature.workflow.yaml
How this command works
This command invokes the workflow-chaining skill with the odoo-position-feature workflow.
The runner reads the YAML, emits a soft-plan-gate, collects required inputs, and executes
four gated phases in sequence:
| Phase | Skill | Purpose |
|---|---|---|
| feature-check | odoo-feature-check |
Verify the feature exists; identify editions and key modules |
| addon-diff | odoo-addon-diff |
Edition capability table (CE / EE / Dist.) |
| competitive-brief | odoo-competitive-brief |
Odoo vs competitor matrix (skipped if no competitor named) |
| positioning-copy | inline | Produce copy block adapted to audience + channel |
Inputs collected at Phase 0
- feature_name - the Odoo feature or capability to position (required)
- target_audience - exec / sales / developer / marketer
- competitor_name - competitor to benchmark against (optional; answer "none" to skip Phase 3)
- output_channel - slide / blog / email / proposal
Output artifacts land under <ISOLATE_DIR>/positioning/ (resolve <SHARE_DIR>/<ISOLATE_DIR> once
per ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md; substitute the captured absolute
path - never write the placeholder or a bare .odoo-ai/ into a Read/Write/Edit).
To run
Invoke this command; workflow-chaining guides you through all phases with explicit
gates between each. To resume an interrupted run, re-invoke with the same feature slug -
the runner reads <ISOLATE_DIR>/positioning/<slug>-state.json automatically.
See also
plugins/odoo-ai-agents/workflows/odoo-position-feature.workflow.yaml- SSOT for phases, gates, model tiers/odoo-ai-agents:odoo-content-draft- full marketing pieces (blog, whitepaper, case study)/odoo-respond-bid- RFP positioning with pricing and timelines/odoo-ai-agents:odoo-objection-handling- reactive objection responses
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.
- 8d ago First seen · 53 lines · 62 tokens per session scan A d551802dfcb0
odoo-position-feature is a command published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 593 once invoked, about $0.0003 per session on Opus 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.