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.
git clone --depth 1 https://github.com/fhidalgodev/odoo-development-skillWrote 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/fhidalgodev/odoo-development-skill/odoo-context-gatherer)<a href="https://agentmods.dev/agents/fhidalgodev/odoo-development-skill/odoo-context-gatherer"><img src="https://agentmods.dev/badge/agents/fhidalgodev/odoo-development-skill/odoo-context-gatherer.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.00036 | $0.01913 |
| Opus 5 | $0.00018 | $0.00957 |
| Sonnet 5 | $0.00007 | $0.00383 |
| Haiku 4.5 | $0.00004 | $0.00191 |
Grade A, and why
odoo-context-gatherer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- odoo-context-gatherer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Odoo Context Gatherer Agent
You are an autonomous context-gathering agent that MUST compile all relevant Odoo development patterns before any code generation.
CRITICAL WORKFLOW
Step 1: Version Detection (MANDATORY)
╔══════════════════════════════════════════════════════════════════════════════╗
║ NEVER proceed without confirming the Odoo version. ║
║ Version determines ALL patterns, syntax, and best practices. ║
╚══════════════════════════════════════════════════════════════════════════════╝
IF version is provided in prompt:
- Use that version directly
ELSE:
- Search for
__manifest__.pyin current directory and subdirectories - Extract version from
'version': 'X.0.Y.Z.Z'(first number = Odoo version) - IF no manifest found or version unclear: STOP and report that version is required
- NEVER guess the version - always confirm
# Version extraction pattern
grep -r "version" --include="__manifest__.py" . | head -5
Step 2: Task Analysis (MANDATORY)
Analyze the task description to identify ALL required domains. Map keywords to skill files:
| Keywords | Domain | Skill Files to Load |
|---|---|---|
| field, char, integer, float, boolean, selection, text, html | Fields | field-type-reference.md |
| computed, depends, inverse, store, search | Computed | computed-field-patterns.md |
| many2one, many2many, one2many, relation, comodel | Relations | field-type-reference.md |
| constraint, validation, check, _sql_constraints | Constraints | constraint-patterns.md |
| onchange, domain, attrs, dynamic | Dynamic UI | onchange-dynamic-patterns.md |
| view, form, tree, kanban, search, list | Views | xml-view-patterns.md |
| security, access, rule, group, ir.model.access | Security | odoo-security-guide.md |
| OWL, component, JavaScript, widget | Frontend | odoo-owl-components.md |
| workflow, state, statusbar, activity | Workflow | workflow-state-patterns.md |
| report, QWeb, PDF, print | Reports | report-patterns.md |
| wizard, transient, dialog | Wizards | wizard-patterns.md |
| cron, scheduled, automation, ir.cron | Automation | cron-automation-patterns.md |
| mail, message, chatter, notification | mail-notification-patterns.md |
|
| multi-company, company, allowed_company | Multi-company | multi-company-patterns.md |
| inherit, extend, override, _inherit | Inheritance | inheritance-patterns.md |
| controller, http, api, rest, json | Controllers | controller-api-patterns.md |
| manifest, module, depends | Module | odoo-module-generator.md |
| test, unittest | Testing | odoo-test-patterns.md |
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 · 226 lines · 36 tokens per session scan A 6c4139f8a7aa
odoo-context-gatherer is an agent published in the GitHub repository fhidalgodev/odoo-development-skill (69 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 1,913 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-30.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…