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-forward-port)<a href="https://agentmods.dev/skills/viindoo/odoo-mcp-client/odoo-forward-port"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-forward-port/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-forward-port"><img src="https://agentmods.dev/badge/skills/viindoo/odoo-mcp-client/odoo-forward-port.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.00242 | $0.21153 |
| Opus 5 | $0.00121 | $0.10577 |
| Sonnet 5 | $0.00048 | $0.04231 |
| Haiku 4.5 | $0.00024 | $0.02115 |
Grade C, and why
odoo-forward-port scanned grade C with 1 finding 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`find <ISOLATE_DIR>/forward-port/ -mindepth 1 -maxdepth 1 -type d -mmin +43200 -exec rm -rf {} +` How it starts
The opening of the file, as written. The whole thing — 1,039 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Forward-port conductor: own the git topology, the per-commit SEMANTIC pipeline, and the subagent
lifecycle. Decide which commit at which model tier, which outcome bucket, when to gate.
The semantic work is per-commit; the git operation is NOT. Intent, bucket, and adapt are
reasoned per source commit; the range is absorbed by ONE merge closed by ONE merge commit.
Delegate leaf tasks to specialist agents and read-only delegates: intent extraction, code adapt,
test forwarding, AND every gate P6 / P6-TEST / P7 runs - the conflict-marker scan and range file
list, the OSM symbol grounding, the static lint lanes, and the test-collection gate (WHO takes
which: [[fp-symbol-survival-check]] - Who runs this check). You record verdicts and finding
lines; you do not produce them.
Core invariant: a forward-port is a SEMANTIC translation, not a git operation. A green
merge + lint + install does NOT prove the feature works on the target platform; only an
intent test that goes red-then-green, plus a symbol-survival check, proves it. SHA is sacred -
continuous forward-port absorbs the source RANGE into the target DAG with a single merge of its
tip, so every source SHA is preserved and the merge-base advances in one step; never squash,
never cherry-pick, and never merge the range one commit at a time.
Out of Scope
- One isolated change with no source commit to port -> use
odoo-coding - A version-to-version API/feature delta only (no merge, no adapt) -> use
odoo-version-diff - Reviewing or auditing an existing PR or diff -> use
odoo-code-review - A pre-upgrade deprecation sweep of one codebase -> use
odoo-deprecation-audit - Same-series single-commit replay (no version jump) -> use
odoo-git-rebase - Whole-cluster upgrade to a higher series (not one commit) -> use
odoo-modules-upgrade - A STANDALONE design request with no commits to port -> use
odoo-solution-designdirectly. A bucket-(c) commit INSIDE a forward-port run that requires non-trivial design is handled by the P3 conditional route-out (which delegates to odoo-solution-design and returns) - that is IN scope of this skill, not a hand-off boundary - Parallelizing N disjoint WIs with cherry-pick + squash semantics -> use
odoo-planning(the USER-facing choice; it plans the node execution forrun-harness, which lands each node by cherry-pick - whereas forward-port keeps SHA by merge: a different git contract)
What ships with it
3 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.
- 7d ago First seen · 1,039 lines · 242 tokens per session scan C 0258e5382c0f
odoo-forward-port is a skill published in the GitHub repository Viindoo/odoo-mcp-client (7 stars, last pushed 5d ago), licensed MIT. It adds 242 tokens to every session and 21,153 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…