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 qwerfunch/cladding --skill oraclegit clone --depth 1 https://github.com/qwerfunch/claddingWrote 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/qwerfunch/cladding/oracle)<a href="https://agentmods.dev/skills/qwerfunch/cladding/oracle"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/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/skills/qwerfunch/cladding/oracle"><img src="https://agentmods.dev/badge/skills/qwerfunch/cladding/oracle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.01265 |
| Opus 5.5 | $0.00033 | $0.00506 |
| Sonnet 5.5 | $0.00016 | $0.00253 |
| Haiku 4.5 | $0.00008 | $0.00127 |
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 1mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cladding oracle — impl-blind conformance authoring
A SPEC_CONFORMANCE oracle is a conformance test authored without seeing the implementation, so a passing oracle means "matches the spec," not "matches the code." The A/B that motivated this: a blind oracle caught bugs a code-peeking (sighted) oracle rubber-stamped (7/8 vs 4/8). cladding owns no LLM — the blinding is your discipline as the host; cladding produces the brief, records provenance, and the gate audits it.
Which ACs need an oracle? (the policy)
A project sets its requirement under spec.yaml::project:
oracle_policy: { always_ears: [unwanted], sample: 0.2 }(RECOMMENDED) — risk-weighted: author an oracle for every done AC whose EARS category is inalways_ears(default['unwanted']— error/edge handling), PLUS a deterministic ~samplefraction of the rest. v8 showed exhaustive per-AC oracles add ~0 quality at ~30% cost, so spot-check the bulk and concentrate verification where failures cluster.require_oracles: true— EXHAUSTIVE (every done AC). Highest assurance, highest cost.oracle_policytakes precedence when both are set.- Neither — no mandate (an authored oracle still runs + is recorded; a missing one is not forced).
Run clad oracle --required to print the worklist — exactly which done ACs the policy demands an oracle
for, which already have one, and why (always:<ears> / sample / exhaustive). Author oracles for the
← needs an impl-blind oracle rows only; do NOT author for ACs the policy did not select.
Protocol (three steps — do them in order)
-
Get the spec-only brief. Run
clad oracle <featureId> --ac <acId>. It prints the acceptance criterion- the module's declaration-only signatures — and NEVER an implementation body. This is the only thing the author may see.
-
Spawn a FRESH, blind sub-agent (the Task tool / a new sub-agent context) handed ONLY that brief. It MUST NOT read
src/or any implementation file. Instruct it to write a vitest conformance suite that asserts only what the criterion literally requires — when the spec is silent on an edge, a WEAKER assertion, not a stronger guess (an over-strict oracle falsely fails correct code). The sub-agent's identity must differ from whoever implemented the feature.
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.
- 1mo ago First seen · 70 lines · 82 tokens per session scan A 11e111ac0a49
oracle is a skill published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 1,265 once invoked, about $0.0003 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 skills, from other repositories
windows-qa-engineer
Use when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP. Triggers on "test this Windows app", "QA the app", "run smoke test", "click the button", "fill the form", "check the UI", "Windows automation", "UFO QA", "verify the dialog", or any Windows desktop UI testing task. Not for…
linked-intent-dev
Guide for linked-intent development (LID). Consult for ALL code changes. Walks changes through a mode-aware six-phase workflow (HLD → LLD → EARS → intent-narrowing edge audit → tests-first → code) with mandatory stops between each phase. Bugs walk the arrow like any other change — no short-circuit. Enforces cascade…
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Enforces red-green-refactor cycle with strict rules.
bug-fix-protocol
8-step disciplined bug-fix protocol that treats every production bug as two failures — the code defect itself and the testing system that allowed it through. Use when fixing a production bug, investigating a regression, writing a post-mortem, or auditing a missed defect. Triggers on "fix this bug", "production bug"…
bidirectional-differential
Audit coherence across an arrow of intent by running two parallel fresh Claude sessions — one reconstructs code from a single EARS, the other reconstructs the EARS from stripped code — then classifies the drift between them. Use when the user invokes /differential-audit, asks to audit EARS-to-code drift for a feature…
mutation-test
Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot…