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 frankxai/claude-skills-library --skill excellence-reviewgit clone --depth 1 https://github.com/frankxai/claude-skills-libraryWrote 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/frankxai/claude-skills-library/excellence-review)<a href="https://agentmods.dev/skills/frankxai/claude-skills-library/excellence-review"><img src="https://agentmods.dev/badge/skills/frankxai/claude-skills-library/excellence-review/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/frankxai/claude-skills-library/excellence-review"><img src="https://agentmods.dev/badge/skills/frankxai/claude-skills-library/excellence-review.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.00061 | $0.00223 |
| Opus 5.5 | $0.00024 | $0.00089 |
| Sonnet 5.5 | $0.00012 | $0.00045 |
| Haiku 4.5 | $0.00006 | $0.00022 |
Grade A, and why
excellence-review 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- excellence-review — 100% identical, 0 lines differ
What it actually says
Excellence Review Skill — Grok Harness
God 99 Mandate
- repo-mastery (read all rules files first, map cross-repo)
- CEO/Eng/Design plan reviews (subagent or delegate to claude)
- Adversarial: verification-loop + santa-method (2 independent pass required)
- gstack: qa (tiers quick/standard/exhaustive), browse, design-review, benchmark, canary
- Security: cso / security-auditor + supply chain
- Polish: rules-distill, skill-comply, document-release
Output format: report + before/after + artifacts. Iterate atomically.
Tools: gstack (headless browser ~100ms), terminal (tests), subagents.
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 · 19 lines · 61 tokens per session scan A 06ec7e523389
excellence-review is a skill published in the GitHub repository frankxai/claude-skills-library (47 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 223 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 skills, from other repositories
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
pr
A writing guide for creating pull request descriptions, which explain a proposed code change to reviewers. It uses sections for the summary, evidence, merge risk, and the likely area affected by the change.
migrate-to-shoehorn
A testing guide for Shoehorn, a TypeScript library that lets tests provide only the fields they need from a larger data type.
code-review
A code-review skill that compares changes from a chosen commit, branch, tag, or merge-base against the repository’s coding standards and the related issue or specification.
improve-codebase-architecture
A skill that scans a codebase for places where restructuring could make future changes and testing easier, then produces an HTML report for selected improvements.
tdd
A reference for Test-Driven Development (TDD), a method where you write a failing test, make it pass, and then improve the code. It covers how to write durable tests, where to place them, and which patterns to avoid.