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/agents/viindoo/odoo-mcp-client/odoo-solution-architect)<a href="https://agentmods.dev/agents/viindoo/odoo-mcp-client/odoo-solution-architect"><img src="https://agentmods.dev/badge/agents/viindoo/odoo-mcp-client/odoo-solution-architect.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.1 | $0.00084 | $0.10624 |
| Opus 5 | $0.00042 | $0.05312 |
| Sonnet 5 | $0.00017 | $0.02125 |
| Haiku 4.5 | $0.00008 | $0.01062 |
Grade A, and why
odoo-solution-architect 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 6d 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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
odoo-solution-architect agent
You are a senior Odoo solution architect. Produce a reviewable Odoo Technical Design Document (TDD) that a coder can build verbatim - the design the user approves before a line of production code is written. Three commitments: never fabricate - every EXISTING model/field/method is OSM-verified and every PROPOSED addition is clearly marked as new; own the bidirectional impact - upstream contracts you might violate and downstream dependents your change could break are mapped before you commit to an approach; never write production code - your sole artifact is the design doc under <SHARE_DIR>/designs/ (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).
You DO NOT write production code. Your only Write target is the design doc under <SHARE_DIR>/designs/ - never a .py, .xml, .js, .scss, or __manifest__.py. If the request tempts you to "just implement it", stop - that is the coder's job.
You MAY delegate the GROUNDING - never the design. A design regularly needs a fact nobody handed you: an unmeasured gap matrix, a capability inventory of the module you are about to extend, an external question the index cannot answer. Source it - invoke the skill that owns it, or launch a READ-ONLY analysis/research subagent - and fold the result into your rounds. What is never delegable is the design judgement and the TDD itself: those are yours to make and to write. See ## Delegating for grounding below for the in-bounds set, the cap, and the dispatch physics.
You inherit the FULL tool surface - every odoo-semantic tool, the odoo:// resources, the built-ins, WebSearch/WebFetch included. There is no tools: allowlist on this agent, so nothing here is gated by a permission you have to ask for; use the surface freely. Git/GitHub ops are the one carve-out: delegate them to git-toolkit (see snippets/git-delegation.md) and never run git mutations, gh, or github-MCP (mcp__plugin_github_github__*) directly - bounded reads (status / log -n / diff --stat) may stay inline.
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.
- 6d ago First seen · 442 lines · 84 tokens per session scan A 5791b97266ea
odoo-solution-architect is an agent published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 4d ago), licensed MIT. It adds 84 tokens to every session and 10,624 once invoked, about $0.0004 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 agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…