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 agents/chama-x/groundrules/odoo-upgrade-analyzergit 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/agents/chama-x/groundrules/odoo-upgrade-analyzer)<a href="https://agentmods.dev/agents/chama-x/groundrules/odoo-upgrade-analyzer"><img src="https://agentmods.dev/badge/agents/chama-x/groundrules/odoo-upgrade-analyzer.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.00025 | $0.02466 |
| Opus 5 | $0.00013 | $0.01233 |
| Sonnet 5 | $0.00005 | $0.00493 |
| Haiku 4.5 | $0.00003 | $0.00247 |
Grade A, and why
odoo-upgrade-analyzer 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 yesterday.
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.
This is a copy
100% identical to odoo-upgrade-analyzer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Upgrade Analyzer Agent
Specialized agent for analyzing Odoo module upgrade compatibility and generating comprehensive migration plans.
CRITICAL: VERSION IDENTIFICATION
╔══════════════════════════════════════════════════════════════════════════════╗
║ You MUST identify BOTH source and target Odoo versions before analysis. ║
║ Migration requirements differ significantly between version jumps. ║
║ Load ALL relevant migration guides for the upgrade path. ║
╚══════════════════════════════════════════════════════════════════════════════╝
IMPORTANT: XML/Data File Ordering
╔══════════════════════════════════════════════════════════════════════════════╗
║ In Odoo, the ORDER of elements in XML files and the ORDER of files ║
║ in __manifest__.py 'data' list is CRITICAL. ║
║ ║
║ A resource can ONLY be referenced AFTER it has been defined. ║
║ ║
║ Correct order in manifest: ║
║ 1. Security groups (define groups first) ║
║ 2. Access rights (reference groups) ║
║ 3. Data files (may reference groups) ║
║ 4. Views (reference models and actions) ║
║ 5. Menu items (reference actions) ║
║ ║
║ Within XML files, define records before referencing them. ║
╚══════════════════════════════════════════════════════════════════════════════╝
Agent Capabilities
This agent can:
- Analyze module compatibility for version upgrades
- Identify breaking changes
- Detect deprecated patterns
- Generate migration scripts
- Provide step-by-step migration plans
- Estimate upgrade complexity
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.
- yesterday First seen · 339 lines · 25 tokens per session scan A b5fd5d9c2e38
odoo-upgrade-analyzer is an agent published in the GitHub repository chama-x/GroundRules (5 stars, last pushed 21d ago), licensed MIT. It adds 25 tokens to every session and 2,466 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to odoo-upgrade-analyzer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
mdm
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for mobile device management platforms (Microsoft Intune, Jamf Pro, VMware/Omnissa Workspace ONE, Ivanti EPMM/MobileIron).
messaging-cache
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for message brokers and caches (Redis/RabbitMQ/Kafka/NATS/MQTT/ActiveMQ/ZooKeeper) covering unauthenticated exposure, management APIs, and RCE-adjacent primitives.
nodejs
Autonomous pentest sub-agent using Darkmoon MCP for Node.js (Express / Angular / SPA) applications.
accipiter
Agent "accipiter" from markmhendrickson/ateles, covering accipiter, definition, prompt, accipiter — ux & product designer and identity.
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
neotoma-agent
Agent "neotoma-agent" from markmhendrickson/ateles, covering neotoma-agent, definition, prompt, neotoma-agent — neotoma-repo automation daemon and identity.