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 agentmods add skills/deepgram/dglabs-deepclaw/oraclenpx skills add deepgram/dglabs-deepclaw --skill oraclegit clone --depth 1 https://github.com/deepgram/dglabs-deepclawWrote 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/deepgram/dglabs-deepclaw/oracle)<a href="https://agentmods.dev/skills/deepgram/dglabs-deepclaw/oracle"><img src="https://agentmods.dev/badge/skills/deepgram/dglabs-deepclaw/oracle.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 | $0.00025 | $0.01315 |
| Opus 5 | $0.00013 | $0.00658 |
| Sonnet 5 | $0.00005 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00131 |
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 4d 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.
This is a copy
100% identical to oracle — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
oracle — best use
Oracle bundles your prompt + selected files into one “one-shot” request so another model can answer with real repo context (API or browser automation). Treat output as advisory: verify against code + tests.
Main use case (browser, GPT‑5.2 Pro)
Default workflow here: --engine browser with GPT‑5.2 Pro in ChatGPT. This is the common “long think” path: ~10 minutes to ~1 hour is normal; expect a stored session you can reattach to.
Recommended defaults:
- Engine: browser (
--engine browser) - Model: GPT‑5.2 Pro (
--model gpt-5.2-proor--model "5.2 Pro")
Golden path
- Pick a tight file set (fewest files that still contain the truth).
- Preview payload + token spend (
--dry-run+--files-report). - Use browser mode for the usual GPT‑5.2 Pro workflow; use API only when you explicitly want it.
- If the run detaches/timeouts: reattach to the stored session (don’t re-run).
Commands (preferred)
-
Help:
oracle --help- If the binary isn’t installed:
npx -y @steipete/oracle --help(avoidpnpxhere; sqlite bindings).
-
Preview (no tokens):
oracle --dry-run summary -p "<task>" --file "src/**" --file "!**/*.test.*"oracle --dry-run full -p "<task>" --file "src/**"
-
Token sanity:
oracle --dry-run summary --files-report -p "<task>" --file "src/**"
-
Browser run (main path; long-running is normal):
oracle --engine browser --model gpt-5.2-pro -p "<task>" --file "src/**"
-
Manual paste fallback:
oracle --render --copy -p "<task>" --file "src/**"- Note:
--copyis a hidden alias for--copy-markdown.
Attaching files (--file)
--file accepts files, directories, and globs. You can pass it multiple times; entries can be comma-separated.
-
Include:
--file "src/**"--file src/index.ts--file docs --file README.md
-
Exclude:
--file "src/**" --file "!src/**/*.test.ts" --file "!**/*.snap"
-
Defaults (implementation behavior):
- Default-ignored dirs:
node_modules,dist,coverage,.git,.turbo,.next,build,tmp(skipped unless explicitly passed as literal dirs/files). - Honors
.gitignorewhen expanding globs. - Does not follow symlinks.
- Dotfiles filtered unless opted in via pattern (e.g.
--file ".github/**"). - Files > 1 MB rejected.
- Default-ignored dirs:
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.
- 4d ago First seen · 126 lines · 25 tokens per session scan A 903a053178a3
oracle is a skill published in the GitHub repository deepgram/dglabs-deepclaw (23 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,315 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to oracle, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…