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-introspectorgit 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-introspector)<a href="https://agentmods.dev/skills/actinon-com/brass-monkey/odoo-introspector"><img src="https://agentmods.dev/badge/skills/actinon-com/brass-monkey/odoo-introspector/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/actinon-com/brass-monkey/odoo-introspector"><img src="https://agentmods.dev/badge/skills/actinon-com/brass-monkey/odoo-introspector.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.00028 | $0.00850 |
| Opus 5 | $0.00014 | $0.00425 |
| Sonnet 5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
odoo-introspector 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Odoo Introspector
This skill provides the agent with the necessary expertise to examine, understand, and interpret Odoo's internal ORM (Object-Relational Mapping) structures and metadata.
Core Mandates
1. Static Resources vs. Live Truth
- Mandate: All static resources (e.g.,
core-models.md,*-fields.json) provided in skills are convenience snapshots of standard Odoo models. They are NOT exhaustive and do NOT include custom fields added via Odoo Studio or third-party modules. - Verification: If a user mentions a field that is not in your resources, or if a task requires absolute technical precision, you MUST call
inspect_modelto retrieve the "Live Truth" from the target Odoo instance. NEVER argue with a user about a field's existence based on a static resource.
2. Baseline Field Assumptions
When inspecting an Odoo model (via inspect_model), you must assume the following baseline for every field unless a property flag explicitly overrides it:
- Storage: The field is stored in the database (
store: true). - Mutability: The field is both readable and writable (
readonly: false). - Optionality: The field is optional (
required: false). - Scope: The field is shared across all companies in the instance (
company_dependent: false). - Translation: The field is NOT translatable (
translate: false).
2. Interpreting Lean Property Encoding
The inspect_model tool uses a compressed "Lean Property Encoding" strategy. Deviations from the baseline assumptions are listed in a properties array:
required: The field MUST be provided during creation.readonly: The field is managed by the system and cannot be manually written.company-dependent: The field value is stored per-company (viair.property).not-stored: The field is computed on-the-fly and cannot be used in direct SQL-like searches unless it is explicitly marked as stored.translatable: The field supports multiple languages. The server handles language synchronization for you.
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.
- 8d ago First seen · 48 lines · 28 tokens per session scan A 053d0e06ff18
odoo-introspector is a skill published in the GitHub repository actinon-com/brass-monkey (2 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 850 once invoked, about $0.0001 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
supabase-cli
This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.
supabase-js
This skill should be used when user asks to "use supabase-js", "query Supabase database", "supabase auth", "supabase storage", "supabase realtime", "supabase edge functions", or works with the @supabase/supabase-js JavaScript/TypeScript SDK.
neo4j-getting-started-skill
Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Each stage reads its own reference file. Supports HITL and fully autonomous operation. Use when starting a new Neo4j project from scratch, provisioning Aura, generating synthetic data, building…
neo4j-graphql-skill
Build and configure a GraphQL API backed by Neo4j using @neo4j/graphql v7 (current) or v5 (LTS). Covers Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints(), type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher for custom resolvers, @authorization/@authentication for JWT/JWKS…
neo4j-kafka-skill
Configure and operate the Neo4j Connector for Kafka (sink + source) and the native Neo4j CDC API. Covers Cypher/Pattern/CUD sink strategies, CDC-based and query-based source, exactly-once semantics, DLQ error handling, Confluent Cloud managed connector, schema registry (Avro/JSON), and native db.cdc.query cursor-loop…
bullmq-specialist
BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue.