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 adewale/skill-eval-harness --skill demogit clone --depth 1 https://github.com/adewale/skill-eval-harnessWrote 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/adewale/skill-eval-harness/demo)<a href="https://agentmods.dev/skills/adewale/skill-eval-harness/demo"><img src="https://agentmods.dev/badge/skills/adewale/skill-eval-harness/demo/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/adewale/skill-eval-harness/demo"><img src="https://agentmods.dev/badge/skills/adewale/skill-eval-harness/demo.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.00028 | $0.00186 |
| Opus 5.5 | $0.00011 | $0.00074 |
| Sonnet 5.5 | $0.00006 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
demo-reviewer 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.
What it actually says
Demo Reviewer
A deliberately tiny skill that exists only to demonstrate the harness end to end (materialized ablations included). It has exactly two load-bearing pieces — a severity rule and a checklist reference — each targeted by one ablation below.
Severity rules
Label every finding with one of: Blocking, Minor, or Clean. State the label explicitly so the reader can triage at a glance. A change that ships without a test is at least Blocking.
Evidence
Back each finding with concrete evidence and follow the shared review checklist: see the review checklist.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 23 lines · 28 tokens per session scan A 10324fae06ce
demo-reviewer is a skill published in the GitHub repository adewale/skill-eval-harness (77 stars, last pushed 14d ago), licensed MIT. It adds 28 tokens to every session and 186 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-08-30.
Other skills, from other repositories
python-style
Validate Python code against style and architectural conventions.
arize-annotation
INVOKE THIS SKILL when creating, managing, or using annotation configs or annotation queues on Arize (categorical, continuous, freeform), or applying human annotations to project spans via the Python SDK. Configs are the label schema for human feedback; queues are review workflows that route records to annotators.…
fast-rust
Practical guidance for writing, refactoring, and reviewing fast, reliable, and maintainable Rust code.
sdlc-readiness-review
Use only when the user explicitly invokes this skill to make a readiness-gate judgment on SDLC materials, specs, handoffs, issues, or direct-dev requests.
dev-git-workflow
Use for non-trivial Git state such as branch strategy, worktrees, merge/rebase decisions, conflicts, reviewer-facing PR preparation, tags, and release notes. Do not trigger for a routine commit, push, or PR that needs no strategy decision.
dev-pr-review
Use for reviewing a branch, pull request, local diff, or implementation plan before merge, including alignment of existing PR metadata with the diff and delivery state.