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.
npx skills add ahmed-lakosha/odoo-plugins --skill theme-designgit clone --depth 1 https://github.com/ahmed-lakosha/odoo-pluginsWrote 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/ahmed-lakosha/odoo-plugins/theme-design)<a href="https://agentmods.dev/skills/ahmed-lakosha/odoo-plugins/theme-design"><img src="https://agentmods.dev/badge/skills/ahmed-lakosha/odoo-plugins/theme-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/ahmed-lakosha/odoo-plugins/theme-design"><img src="https://agentmods.dev/badge/skills/ahmed-lakosha/odoo-plugins/theme-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.00235 | $0.02192 |
| Opus 5 | $0.00118 | $0.01096 |
| Sonnet 5 | $0.00047 | $0.00438 |
| Haiku 4.5 | $0.00023 | $0.00219 |
Grade A, and why
theme-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 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma-to-Odoo Design Workflow
Design Workflow Methodology
1. ANALYZE DESIGN → Extract colors, fonts, layout, components
2. COMPARE TO ODOO TEMPLATES → Match header, footer, page layouts
3. CHOOSE CLOSEST TEMPLATE → Select best matching built-in template
4. CONFIGURE VIA VARIABLES → Set $o-website-values-palettes
5. ENHANCE WITH CUSTOM CSS → Only what templates can't provide
6. CREATE CUSTOM SNIPPETS → Components not available in Odoo
Figma Extraction Pipeline
Using Figma MCP
1. Use Figma MCP with prompt:
"Convert this Figma design to HTML for Odoo <version> website theme.
Use Bootstrap v5.1.3 classes (not Tailwind).
Apply proper Odoo theme structure with sections and containers."
2. Extract Color Palette:
"Extract the color palette and map to o-color-1 through o-color-5."
3. Extract Typography:
"Convert text styling to Bootstrap typography classes."
Using Chrome MCP (Browser Automation)
- Navigate to Figma URL → Open Pages (not components!)
- Click on page elements to extract:
- Header/navbar → primary color
- CTA buttons → secondary color
- Section backgrounds → o-color-3
- Body text → text color, font family
- Headings (H1-H6) → heading fonts, sizes
Pages to check: Homepage, About/Services, Contact, Footer area
Color Mapping
| Design Element | Maps To |
|---|---|
| Primary brand color (buttons, links) | o-color-1 |
| Accent/CTA color | o-color-2 |
| Light section backgrounds | o-color-3 |
| Main content background | o-color-4 |
| Dark text / headings | o-color-5 |
Header Templates (11 Primary + Variants)
| XML ID | Name | Best For |
|---|---|---|
website.template_header_default |
Default | Most websites |
website.template_header_hamburger |
Hamburger | Minimal designs |
website.template_header_stretch |
Stretch | Wide layouts |
website.template_header_vertical |
Vertical | App-like sites |
website.template_header_search |
Search | E-commerce, directories |
website.template_header_sales_one |
Sales 1 | Online stores |
website.template_header_sales_two |
Sales 2 | Large catalogs |
website.template_header_sales_three |
Sales 3 | Product-focused |
website.template_header_sales_four |
Sales 4 | Fashion, retail |
website.template_header_sidebar |
Sidebar | Dashboard sites |
website.template_header_boxed |
Boxed | Modern brands |
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 · 272 lines · 235 tokens per session scan A 9ea7e60c2a72
theme-design is a skill published in the GitHub repository ahmed-lakosha/odoo-plugins (74 stars, last pushed 5mo ago), licensed MIT. It adds 235 tokens to every session and 2,192 once invoked, about $0.0012 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-30.
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 $ralph 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…