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 actinon-com/brass-monkey --skill odoo-plmgit clone --depth 1 https://github.com/actinon-com/brass-monkeyWrote 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/actinon-com/brass-monkey/odoo-plm)<a href="https://agentmods.dev/skills/actinon-com/brass-monkey/odoo-plm"><img src="https://agentmods.dev/badge/skills/actinon-com/brass-monkey/odoo-plm.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.00031 | $0.00431 |
| Opus 5 | $0.00015 | $0.00216 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
odoo-plm 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 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.
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
Skill: Odoo PLM (Product Lifecycle Management)
This skill provides the agent with high-level functional expertise in Odoo's PLM module, covering Engineering Change Orders (ECO), BoM versioning, and change approvals.
Core Mandates
1. Structure of a Change (ECO)
- Proposed Changes: Instead of modifying a live BoM, use an Engineering Change Order (
mrp.eco) to propose modifications. - Types: ECOs are categorized by Type (
mrp.eco.type), such as 'BoM Change' or 'Routing Change'. - Workflow: ECOs move through Stages (
mrp.eco.stage).
2. Prohibited Direct Edits
- Mandate: If the PLM module is installed, the agent is strictly forbidden from using
write_recordto modify an activemrp.bom. All changes must be routed through anmrp.eco.
3. Change Tracking
- BoM Changes (
mrp.eco.bom.change): Tracks the addition, removal, or quantity update of components. - Routing Changes (
mrp.eco.routing.change): Tracks modifications to manufacturing operations or work center assignments.
4. Approvals & Application
- Approval Flow: Each stage can require one or more approvals. Use
search_readonmrp.eco.approvalto verify if a change is ready to be applied. - Applying Changes: Once approved and moved to the "Apply" stage, Odoo archives the old BoM version and activates the new version created by the ECO.
Available Resources
plm-logic.md: Deep-dive into version control, conflict resolution, and effectivity dates.plm-fields.json: Dense technical map of fields for ECO, Type, Stage, and Change models.
What ships with it
2 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 · 30 lines · 31 tokens per session scan A 96543174d378
odoo-plm is a skill published in the GitHub repository actinon-com/brass-monkey (2 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 431 once invoked, about $0.0002 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
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
spk-run-verdict-capture
Set a Spec Kitty work-package review verdict through the deterministic event-log seam, so every agent harness records approve/reject the same way.
spk-run-implement-review
Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.
spk-admin-dashboard
Open or report the Spec Kitty dashboard. Use for dashboard URL, localhost daemon metadata in .kittify/.dashboard, --open, --kill, or status views.
spk-start-first-feature
Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.