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-migrationnpx skills add chama-x/GroundRules --skill odoo-migrationgit 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-migration)<a href="https://agentmods.dev/skills/chama-x/groundrules/odoo-migration"><img src="https://agentmods.dev/badge/skills/chama-x/groundrules/odoo-migration.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 | $0.00068 | $0.00435 |
| Opus 5 | $0.00034 | $0.00217 |
| Sonnet 5 | $0.00014 | $0.00087 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
odoo-migration 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 4d 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 Migration
Use this skill for OCA module migration between Odoo major versions.
This is not an OpenUpgrade skill. Do not use OpenUpgrade workflows, commands, upgrade_analysis.txt, or data-model migration analysis as the operating model. If a migration requires project-specific data handling, inspect the addon and repo conventions directly.
First Move
Identify:
- source Odoo version
- target Odoo version
- OCA repository name
- module path/name
- current branch and remotes
- whether the corresponding OCA migration issue or PR context is known
If the Odoo framework source or local development setup is needed and not inside the workspace, ask the user to set ODOO_SOURCE=/path/to/odoo, ODOO_BASE_COMMAND="...", and ODOO_TOOL_README=/path/to/README.md as needed.
Workflow
Use OCA-MODULE-MIGRATION.md as the end-to-end guide.
Always apply every intermediate version checklist for jumps across more than one major version. Example: migrating 15.0 to 18.0 requires the 16.0, 17.0, and 18.0 sections.
Guardrails
- Keep migration compatibility changes separate from behavior changes where possible.
- Do not change copyright years.
- Do not change original authors.
- Do not invent migration script style without repo precedent.
- Do not run Odoo install/update/test commands until likely commands are discovered from repo docs,
$ODOO_TOOL_README, or$ODOO_BASE_COMMAND, and confirmed by the user. - Prefer OCA PR title format:
[<target>][MIG] <module>: Migration to <target>.
What ships with it
1 file 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.
- 4d ago First seen · 39 lines · 68 tokens per session scan A f110e8585bc2
odoo-migration is a skill published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 20d ago), licensed MIT. It adds 68 tokens to every session and 435 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 skills, from other repositories
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.
openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.