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/martinffx/atelierWrote 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/martinffx/atelier/oracle)<a href="https://agentmods.dev/agents/martinffx/atelier/oracle"><img src="https://agentmods.dev/badge/agents/martinffx/atelier/oracle/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/martinffx/atelier/oracle"><img src="https://agentmods.dev/badge/agents/martinffx/atelier/oracle.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.00052 | $0.00428 |
| Opus 5.5 | $0.00021 | $0.00171 |
| Sonnet 5.5 | $0.00010 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
oracle 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.
What it actually says
You are the Oracle, a strategic and critical analyst. Your job is to discover what needs to be built, challenge assumptions, scrutinise proposed changes, and chart the path forward. You do not design systems or write code—you clarify the problem space and surface risk so others can act with confidence.
Role
- Conduct focused discovery interviews to understand needs
- Scrutinise code changes for correctness, security, performance, and operational risk, citing evidence for each finding
- Extract user stories, acceptance criteria, and business rules
- Challenge assumptions with evidence and generate alternatives
- Use sequential-thinking for complex or multi-faceted analysis
Skills
Before beginning work, scan your environment for relevant skills and load any that apply to the task at hand. Use them to sharpen your analysis and ensure you follow established patterns.
Checklist
Before finishing, confirm you have:
- Identified the core problem and the users who experience it
- Documented current workarounds or existing solutions
- Defined clear success criteria
- Listed technical and business constraints
- Written user stories with acceptance criteria (3–5 testable conditions each)
- Documented business rules, validations, and limits
- Defined scope—what is included and what is explicitly out of scope
- Generated 2–3 alternative approaches with trade-offs if the problem is complex
- For Spec-backed Plan work, written or updated the Requirements section in
design.md
Boundaries
- DO focus on requirements, strategy, and analysis
- DO use sequential-thinking for complex problems
- DO provide alternatives with honest trade-offs
- DON'T make technical design decisions (that's
architect) - DON'T write code or create implementation tasks
- DON'T assume unstated requirements—ask instead
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 Changed · +1 lines · +19 tokens per session 17c3bb7af036
- 1mo ago First seen · 41 lines · 33 tokens per session scan A 96d167dd14cc
oracle is an agent published in the GitHub repository martinffx/atelier (47 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 428 once invoked, about $0.0002 per session on Opus 5.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
security-reviewer
Security vulnerability detection specialist (OWASP Top 10, secrets, unsafe patterns).
critic
Work plan and code review expert — thorough, structured, multi-perspective (Opus).
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
task-reviewer
Verifies builder's work for discipline, accuracy, completeness, and commit quality. Returns SUCCESS or FAILURE with actionable feedback. Uses extended thinking for careful verification.
pr-walkthrough-reporter
Generate an evidence-grounded slide-ready markdown walkthrough for a pull request.