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 HoangNguyen0403/agent-skills-standard --skill skill-benchmarkgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/skill-benchmark)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/skill-benchmark"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/skill-benchmark/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/hoangnguyen0403/agent-skills-standard/skill-benchmark"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/skill-benchmark.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.00016 | $0.00739 |
| Opus 5.5 | $0.00006 | $0.00296 |
| Sonnet 5.5 | $0.00003 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
skill-benchmark 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 19d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Benchmark Skill
[!IMPORTANT] Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
📊 Skill Benchmark Orchestrator
Goal: Quantify how much active skills improve implementation quality. Deliver a prioritized compliance delta and skill applicability report.
Step 1 — Project Context & Active Skills
Identify the tech stack and all active skills in AGENTS.md.
# 1. Total source files and lines changed
find src -name "*.ts" -o -name "*.tsx" | xargs wc -l 2>/dev/null | sort -rn | head -20
# 2. Check active skill registry
cat AGENTS.md | head -80
Step 2 — Auto-Select a Legacy Trap
Pick the file automatically. Rank candidates by the severity of anti-patterns:
- 🔴 P0: Hardcoded secrets; Logic inside UI components.
- 🟠 P1: Wrong Router pattern; Global state for local concerns; Missing design tokens.
- 🟡 P2: Raw user-facing strings (i18n).
Step 3 — Build Eval-Driven Scorecard
Source scorecard from evals/evals.json. Distinguish structural checks, textual transcript assertions, and executable verifier outcomes. Never add canned assertion keywords to skills to artificially inflate scores (no answer-anchor padding).
Follow the Scorecard Rubric in <SKILLS>/common/common-skill-creator/references/benchmark.md when synced:
- Read
<SKILLS>/<category>/<skill>/evals/evals.json. - Generate columns for Failure Pattern and Success Pattern.
- Refactor the file, citing the exact skill rule for each change.
- For guardrail skills, read
pressure_scenarios,rationalizations,red_flags, andbehavior_assertions.
Step 4 — Benchmark Report & Evidence Breakdown
Output scorecard and evidence breakdown using templates in <SKILLS>/common/common-skill-creator/references/benchmark.md when synced.
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.
- 19d ago Changed · -4 lines a5f5179a9450
- 27d ago Changed · +1 lines d7d59d734a37
- 1mo ago First seen · 93 lines · 16 tokens per session scan A 2cc98735a90d
skill-benchmark is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 739 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
browser-automation
Playwright browser automation via MCP. Covers E2E testing, UI review, web scraping, screenshot capture, and general browser interaction. MCP-first — CLI is fallback only.
vue-idioms
Vue 3 Composition API patterns: syntax, reactive state with Pinia stores, reusable composables, and Vitest component testing. Use when developing or refactoring Vue 3 frontend applications.
python-idioms
Modern Python (3.11+) idioms: type annotations, typing Protocols, Pydantic models, asyncio, pytest fixtures, and Ruff/Mypy strict compliance. Use when writing, refactoring, or reviewing Python applications, APIs, or scripts.
mobile-testing
Mobile E2E testing patterns — Flutter integrationtest, Patrol, Maestro, golden testing, device matrix, and test data management. Use when writing E2E tests for mobile applications.
testability-patterns
Implementation examples for the three testability rules (I/O isolation, pure logic, dependency direction) across Go, TypeScript, Python, Rust, and Dart. Loaded by reference from architectural-pattern.md — not triggered by file patterns.
testing-strategy
Detailed testing reference material: test doubles strategy, integration test infrastructure (Testcontainers, Firebase emulator), naming conventions per language, test organization patterns. Load when writing tests or setting up test infrastructure. The core mandates (TDD, AAA, pyramid) are in the testing-strategy rule…