oracle

An engineering advice tool with three modes: recommendations, risk analysis, and weighted comparisons of technical options.

In plain words
What is it for?
Use it for design advice, premortems that ask what could go wrong, and comparisons of approaches with their advantages and disadvantages.
Why use it?
It gives developers a structured way to reason about architecture, possible failures, trade-offs, and technology choices.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/darkroomengineering/cc-settings/oracle
Any agent
npx skills add darkroomengineering/cc-settings --skill oracle
Clone the repo
git clone --depth 1 https://github.com/darkroomengineering/cc-settings

Made for: Claude Code, Codex.

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,977 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00061 $0.01977
Opus 5 $0.00030 $0.00988
Sonnet 5 $0.00012 $0.00395
Haiku 4.5 $0.00006 $0.00198

Measured 2d ago against content hash 80111763a5b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

skills/oracle/SKILL.md · 271 lines

How it starts

The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Oracle

Three-mode expert consultation: Advice for architectural guidance, Risks for premortem analysis, Compare for weighted approach evaluation.

Product-direction asks ("what should we build", positioning, market fit) belong to /strategist — a standing persona that explores the codebase for vision framing; this skill is a single-shot engineering consult.

Mode: Advice

How to Answer

  1. Understand the context - What is the user trying to achieve?
  2. Consider trade-offs - What are the pros/cons of different approaches?
  3. Recommend clearly - Give a definitive recommendation
  4. Explain why - Justify your recommendation
  5. Provide examples - Show, don't just tell

Response Format

## Recommendation
[Clear recommendation]

## Why
[Reasoning and trade-offs]

## Example
[Code or implementation example]

## Alternatives
[Other valid approaches and when to use them]

Remember

  • Prioritize Darkroom conventions
  • Store valuable insights as learnings

Mode: Risks

Analyze potential failure modes before they happen.

Purpose

Imagine the project has failed. What went wrong?

This technique surfaces risks that optimism bias might hide.

Analysis Framework

1. Technical Risks
  • What could break?
  • What dependencies might fail?
  • What edge cases are unhandled?
  • What performance issues might emerge?
2. Integration Risks
  • How might this affect other parts of the system?
  • What backwards compatibility issues exist?
  • What migration challenges are there?
3. Operational Risks
  • What could go wrong in production?
  • What monitoring is missing?
  • What recovery procedures are needed?
4. User Experience Risks
  • How might users misuse this?
  • What accessibility issues exist?
  • What confusion might arise?

Output Format

## Premortem: [Feature/Change]

### High Risk
- [Critical failure mode]
  → Mitigation: [How to prevent]

### Medium Risk
- [Significant issue]
  → Mitigation: [How to address]

### Low Risk
- [Minor concern]
  → Mitigation: [Simple fix]

### Recommendations
1. [Priority action]
2. [Secondary action]
3. [Nice to have]

Read the full file on GitHub · 271 lines

Changes

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.

  1. 2d ago First seen · 271 lines · 61 tokens per session scan A 80111763a5b8

Subscribe to this mod's changes

oracle is a skill published in the GitHub repository darkroomengineering/cc-settings (42 stars, last pushed 4d ago), licensed MIT. It adds 61 tokens to every session and 1,977 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

dotfiles-bootstrap

Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.

sebastienrousseau/dotfiles · 88 tokens

astro-dso-doc

Generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), AND a ready-to-paste PixInsight project Description field for a deep-sky object (DSO) astrophotography project. Use this skill whenever the user mentions astrophotography, a DSO…

jjmartres/ai-coding-agents · 244 tokens

document-code

Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go…

jjmartres/ai-coding-agents · 88 tokens

work-on-ticket

Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.

jjmartres/ai-coding-agents · 41 tokens

datadog

Use this skill when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.

jjmartres/ai-coding-agents · 51 tokens

document-project

Generate comprehensive, professional project documentation structures including README, ARCHITECTURE, USERGUIDE, DEVELOPERGUIDE, and CONTRIBUTING files. Use when the user requests project documentation creation, asks to "document a project", needs standard documentation files, or wants to set up docs for a new…

jjmartres/ai-coding-agents · 79 tokens