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 ahmedawan-oracle/claude-code-plugins --skill medallion-authorgit clone --depth 1 https://github.com/ahmedawan-oracle/claude-code-pluginsWrote 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/ahmedawan-oracle/claude-code-plugins/medallion-author)<a href="https://agentmods.dev/skills/ahmedawan-oracle/claude-code-plugins/medallion-author"><img src="https://agentmods.dev/badge/skills/ahmedawan-oracle/claude-code-plugins/medallion-author.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.1 | $0.00157 | $0.05198 |
| Opus 5 | $0.00078 | $0.02599 |
| Sonnet 5 | $0.00031 | $0.01040 |
| Haiku 4.5 | $0.00016 | $0.00520 |
Grade A, and why
medallion-author 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 6d 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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
medallion-author — Tier-2 overlay-author skill
When aidp-fusion-autopilot bootstrap cannot mechanically resolve a
variation point (no candidate the pack declares is present on the
tenant's bronze), it writes a diagnostic artifact and exits non-zero.
This skill is the recovery path: read the artifact, propose new
candidates from the observed bronze schema, present a draft overlay
for operator approval, and draft a remediation runbook. The operator
runs bootstrap --refresh with the overlay applied; bootstrap commits the
resolution.
Architectural authority: docs/workflow.md,
docs/project_setup.md, and docs/aidpf-error-codes.md are current
guidance. The skill is operator-initiated, drafts overlay candidates only,
and never writes profile resolutions directly.
When to use
- The CLI exited 1 with
AIDPF-2010orAIDPF-2011. - A
run --mode seed/incrementalleft anAIDPF-4071__<node>.jsondiagnostic under.aidp/diagnostics/<run_id>/— a bronze node declares a column the live PVO doesn't expose (see the dedicated section below). - The operator wants to author a pack overlay extending the starter pack with new variation-point candidates observed on their tenant.
- Mid-Fusion-upgrade recovery: a column got renamed and the existing candidate list no longer matches.
When NOT to use
- During
run --mode seed/run --mode incremental— the engine has zero LLM dependency at runtime. This skill is operator-initiated and runs between bootstraps. - When the diagnostic artifact is missing — the skill refuses to
invent context (no synthesised proposals from thin air). Exception: the
COA-depth mode (below) is explicitly operator-input driven and runs with
NO diagnostic artifact — its trigger (
AIDPF-2015, acontent-pack validatefailure) writes none. - When
AIDPF-1020is present — operator-identity gate is unrelated to overlay drafting; fix the identity environment first. - To author NEW silver/gold nodes (a SQL template the pack doesn't declare). The skill only EXTENDS existing variation-point candidate lists.
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.
- 6d ago First seen · 436 lines · 157 tokens per session scan A 92cb71d19441
medallion-author is a skill published in the GitHub repository ahmedawan-oracle/claude-code-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 157 tokens to every session and 5,198 once invoked, about $0.0008 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…