Borrowing it
Nothing to install: this file belongs to chama-x/GroundRules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chama-x/GroundRules/master/.agents/skills/odoo-patterns/agents/odoo-upgrade-analyzer.mdgit 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/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/agents/chama-x/groundrules/odoo-upgrade-analyzer"><img src="https://agentmods.dev/badge/agents/chama-x/groundrules/odoo-upgrade-analyzer.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.00025 | $0.02466 |
| Opus 5.5 | $0.00010 | $0.00986 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to odoo-upgrade-analyzer — 58 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.
- 1mo ago 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 2mo ago), licensed MIT. It adds 25 tokens to every session and 2,466 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to odoo-upgrade-analyzer, differing in 58 lines, and is treated as a copy.
Other agents, from other repositories
backend-developer
Use when a ticket needs API or backend work — endpoints, data models, auth, integrations, infra-as-code. Only spawned when backend is in scope per the architecture doc. Runs in parallel with mobile devs on independent tickets.
backend-engineer
General-purpose backend implementer for the user-search feature. Owns API handlers, request validation, RBAC scoping, query builders, cache logic, observability instrumentation, and rate limiting. Triggers - "implement task.
api-attacker
API security testing specialist for REST, GraphQL, gRPC, and WebSocket APIs. Handles BOLA/IDOR, mass assignment, authentication bypass, rate limit evasion, JWT attacks, GraphQL introspection abuse, API enumeration, and OWASP API Top 10. Triggers on: API, REST, GraphQL, gRPC, WebSocket, BOLA, IDOR, mass assignment, API…
ciel-web-guild
CIEL's elite full-stack web guild. Specializes in React, Vue, Svelte, Next.js, Django, Rails, and Laravel.
backend-generator
Backend coding agent. Implements backend sprints from the product spec, one feature at a time. Focuses on API correctness, data integrity, test coverage, and robust error handling. Use for backend implementation sprints.
architect
System architecture and design specialist. Use for designing scalable systems, making architectural decisions, creating technical specifications, or refactoring system structure.