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 bdfinst/agentic-dev-team --skill init-plugin-evalgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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/bdfinst/agentic-dev-team/init-plugin-eval)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/init-plugin-eval"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/init-plugin-eval.svg" alt="Measured on agentmods" 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.00085 | $0.00909 |
| Opus 5 | $0.00043 | $0.00454 |
| Sonnet 5 | $0.00017 | $0.00182 |
| Haiku 4.5 | $0.00009 | $0.00091 |
Grade A, and why
init-plugin-eval 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 2d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init Plugin Eval
Role: implementation. Create the eval scaffold so a plugin's review agents and advisory skills can be graded — without shipping any of it inside the plugin.
Constraints
- Evals never ship. The eval tree lives at the repo root under
evals/<plugin>/, never underplugins/<plugin>/. Build/test tooling inside a plugin dir is a shipping bug. - Stub, don't fake. Scaffold empty
fixtures/andexpected/dirs and a README. Do not invent fixtures — an empty scaffold must grade as "no fixtures", a clean no-op, not an error. - Never overwrite. If
evals/<plugin>/exists, report and stop.
Step 1 — Parse
NAME=$0(the plugin name, matching itsplugin.jsonname).DIR=--dirvalue, elseevals/<NAME>.- If
DIRexists → report and stop.
Step 2 — Create the structure
mkdir -p "$DIR/fixtures" "$DIR/expected"
for d in fixtures expected; do : > "$DIR/$d/.gitkeep"; done
fixtures/— input artifacts an agent/skill runs against (sample agent files, plugin dirs, prose use-cases).expected/— one<fixture-stem>.jsonper fixture declaring the expected grading (which agent/skill it targets and the pass condition).
Step 3 — Write the grading-contract README
$DIR/README.md documents the contract a grader enforces:
# Eval corpus — <NAME>
Fixtures (`fixtures/`) and their expected gradings (`expected/*.json`) for the
<NAME> plugin's review agents and advisory skills.
## Grading contract
Each `expected/<stem>.json` pairs with a `fixtures/<stem>.*` input and declares:
- `fixture` — the fixture file/dir this grades.
- `description` — what the fixture exercises.
- `applicableAgents` / `applicableSkills` — the unit(s) under test.
- For a **review agent**: `expectedStatus` (`pass|warn|fail|skip`),
`issueCount` ({min,max}), and `severities` bounds.
- For an **advisory skill**: the expected `recommendation`/fields and the
rule citations or gates the output must contain.
A grader pairs every `expected/*.json` with a fixture and checks the actual
output falls within the declared bounds. An **empty corpus grades as
"no fixtures"** — a clean no-op, never an error.
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.
- 2d ago First seen · 93 lines · 85 tokens per session scan A 26ef83a718c4
init-plugin-eval is a skill published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 909 once invoked, about $0.0004 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-09-05.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.