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/skills/viindoo/odoo-mcp-client/odoo-frontend-design)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-frontend-design"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-frontend-design/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/skills/viindoo/odoo-mcp-client/odoo-frontend-design"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-frontend-design.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.00226 | $0.02516 |
| Opus 5 | $0.00113 | $0.01258 |
| Sonnet 5 | $0.00045 | $0.00503 |
| Haiku 4.5 | $0.00023 | $0.00252 |
Grade A, and why
odoo-frontend-design 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Senior Odoo frontend designer. The design-quality brain - the body of taste and judgement that decides what "good" looks like inside Odoo, before a line of JS/QWeb/SCSS is written and while it is being reviewed. Carries expertise, not actions: never spawns subagents, never calls the Skill tool, never writes production code.
Out of Scope
- Writing JS / OWL / QWeb / SCSS →
odoo-coding(frontend leg; this skill supplies taste, that bundle owns mechanics) - Rating a rendered screen in a live browser →
odoo-ui-review(six-lens runtime audit; this skill defines the bar it rates against) - Backend Python/XML / data model →
odoo-coding; whole-solution design →odoo-solution-design - Token-reality verification mechanics →
${CLAUDE_PLUGIN_ROOT}/skills/_shared/odoo-frontend-fidelity.md(SSOT; this skill points there, does not restate them)
The core principle: distinctiveness WITHIN constraints
Odoo UI fails in two opposite ways - good design is the ridge between them.
| Cliff (left) | The ridge | Cliff (right) |
|---|---|---|
| Generic, characterless, "AI default" | Distinctive WITHIN Odoo's design system | Off-theme custom look that clashes with the web client |
Great Odoo UI feels like Odoo shipped it - and is still unmistakably well-made. Distinctiveness comes from hierarchy, density, clarity, and restraint executed unusually well, not from inventing a parallel visual language. The website/portal side (Context B) has more freedom than the backend (Context A); the two contexts have different rules.
Odoo's design system already solves spacing, color semantics, focus states, density, and responsive behavior consistently across thousands of screens. Reusing it means a custom screen inherits all of that for free. Inventing your own throws that away and you re-solve (usually worse) what the platform already solved.
Context A - Backend / web client
High-constraint: forms, list/tree, kanban, pivot/graph/calendar/activity/gantt, search/filter, OWL components, QWeb, field widgets. The user is a knowledge worker doing repetitive data work, often all day. Speed, scannability, and predictability beat novelty.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 169 lines · 226 tokens per session scan A 96b8169ab82f
odoo-frontend-design is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 5d ago), licensed MIT. It adds 226 tokens to every session and 2,516 once invoked, about $0.0011 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-09-03.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…