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 agentmods add skills/chama-x/groundrules/odoo-owlnpx skills add chama-x/GroundRules --skill odoo-owlgit clone --depth 1 https://github.com/chama-x/GroundRulesWrote 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/chama-x/groundrules/odoo-owl)<a href="https://agentmods.dev/skills/chama-x/groundrules/odoo-owl"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo-owl.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.00090 | $0.00512 |
| Opus 5 | $0.00045 | $0.00256 |
| Sonnet 5 | $0.00018 | $0.00102 |
| Haiku 4.5 | $0.00009 | $0.00051 |
Grade A, and why
odoo-owl 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 5d 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.
What it actually says
Odoo OWL
Use this skill for OWL frontend work in Odoo addons or standalone Owl applications.
First Move
Do not assume OWL 3. First detect the actual OWL/Odoo frontend version from local source and project code:
- Odoo version from branch, manifests, docs, or config.
- Local OWL source under
$ODOO_SOURCEwhen set, especiallyaddons/web/static/lib/owlor equivalent. - Existing imports from
@odoo/owl,owl,@web/*, and local frontend conventions. - Asset declarations in
__manifest__.pyand existingstatic/src/js,static/src/xml, andstatic/src/scsspatterns.
Use the OWL 3 references only when the target project actually uses OWL 3. For older Odoo versions, local source and existing project conventions supersede this skill's OWL 3 notes.
Route The Task
- Build or change OWL components: use OWL3-CORE.md, OWL3-TEMPLATES.md, and OWL3-STATE-LIFECYCLE.md.
- Integrate with Odoo assets/web client: use OWL3-ODOO-INTEGRATION.md.
- Migrate OWL 1/2 code toward OWL 3: use OWL3-MIGRATION.md, but verify local compatibility first.
- Review frontend guideline/style concerns: compose with
odoo-code-review. - Debug broken Odoo frontend behavior: compose with
odoodebugging workflow and inspect browser/asset/test seams.
Always Apply
Keep UI state explicit and reactive. Prefer small components with clear props and events. Avoid mutating props. Clean up listeners and external resources with lifecycle hooks. Treat unsafe HTML as a security boundary. Verify asset bundle registration and template loading before blaming OWL behavior.
What ships with it
5 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.
- 5d ago First seen · 32 lines · 90 tokens per session scan A 2d5500ec927e
odoo-owl is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 22d ago), licensed MIT. It adds 90 tokens to every session and 512 once invoked, about $0.0005 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 skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-pagerank-analyzer
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.
agent-neural-network
Agent skill for neural-network - invoke with $agent-neural-network.
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.