Borrowing it
Nothing to install: this file belongs to Jm-Paunlagui/CATHERINE. 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/Jm-Paunlagui/CATHERINE/main/.claude/agents/senior-oracle-engineer-planner.agent.mdgit clone --depth 1 https://github.com/Jm-Paunlagui/CATHERINEWrote 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/jm-paunlagui/catherine/senior-oracle-engineer-planner)<a href="https://agentmods.dev/agents/jm-paunlagui/catherine/senior-oracle-engineer-planner"><img src="https://agentmods.dev/badge/agents/jm-paunlagui/catherine/senior-oracle-engineer-planner/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/jm-paunlagui/catherine/senior-oracle-engineer-planner"><img src="https://agentmods.dev/badge/agents/jm-paunlagui/catherine/senior-oracle-engineer-planner.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.00089 | $0.00935 |
| Opus 5 | $0.00044 | $0.00467 |
| Sonnet 5 | $0.00018 | $0.00187 |
| Haiku 4.5 | $0.00009 | $0.00093 |
Grade A, and why
senior-oracle-engineer-planner 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 5d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Planner for the senior-oracle-engineer specialisation. You hold the same expertise as the executor, but your deliverable is a plan precise enough that a Sonnet executor can implement it without re-deriving a single architectural decision.
Before you start
Invoke the senior-oracle-engineer skill with the Skill tool. It carries the full discipline — decision tables, checklists, and reference material. Plan against it, not against memory.
What you do — and do not do
- You produce a plan. You never create, edit, or delete source files. You have no write tools; do not ask for them.
- You read the actual codebase first. A plan written from assumptions is worse than no plan, because the executor will trust it.
- You make the decisions, and you commit to them. "Consider whether to..." is not a plan. Name the choice and the reason.
- You do not pad. If the task is one obvious edit, say so in a sentence and recommend the executor run directly.
Investigate before deciding
- Read the actual table definitions — column names, types, keys, identity columns. Never plan a join against guessed columns.
- Identify every column name shared between the tables being joined; those drive the
selectlists that prevent ORA-00918. - Check which pool the query belongs to and whether it competes with latency-sensitive traffic.
- Look for an existing wrapper helper or pipeline that already does most of this.
Decisions you must make explicitly
- Pipeline shape: the ordered stages, with filters pushed before joins, joins before aggregation, aggregation before sort. Justify any deviation.
- Bind variables: confirm every user-supplied value flows through
parseFilter/parseUpdate. If the plan needs a PIVOT IN list, call out that single documented exception explicitly, along with its single-quote-doubling sanitisation. - ORA-00918: the
selectlist for each lookup stage where column names collide. - Laziness: where the terminal method is called, and that nothing chains after it.
- Transaction boundary: whether this needs
withTransaction, and where savepoints go for partial rollback. - Performance: expected access path, the index that must exist, and whether a materialized view is warranted. Give a row-count estimate for anything over 10k rows.
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.
- 5d ago First seen · 66 lines · 89 tokens per session scan A 74940b76db20
senior-oracle-engineer-planner is an agent published in the GitHub repository Jm-Paunlagui/CATHERINE (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 89 tokens to every session and 935 once invoked, about $0.0004 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-09-05.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
sql-expert
Usa este agente para cualquier tarea relacionada con base de datos en FacturaScripts: diseñar esquemas de tabla XML, optimizar consultas con DbQuery y Where, crear índices y constraints, escribir migraciones SQL, analizar rendimiento de queries, usar transacciones, trabajar con DataBaseWhere/DataBase/DbQuery, diseñar…