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 tjboudreaux/cc-plugin-engineering-excellence --skill eng-verificationgit clone --depth 1 https://github.com/tjboudreaux/cc-plugin-engineering-excellenceWrote 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/tjboudreaux/cc-plugin-engineering-excellence/eng-verification)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-engineering-excellence/eng-verification"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-engineering-excellence/eng-verification/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/tjboudreaux/cc-plugin-engineering-excellence/eng-verification"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-engineering-excellence/eng-verification.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.00028 | $0.00636 |
| Opus 5 | $0.00014 | $0.00318 |
| Sonnet 5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
eng-verification 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 10d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Completion
Overview
Claiming success without evidence is dishonesty, not efficiency. Every status report, “done,” or “tests pass” statement requires fresh verification.
Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you didn’t run the verifying command in this message, you cannot claim it passes.
Gate Function
1. IDENTIFY: Which command proves the claim?
2. RUN: Execute the full command now (fresh run).
3. READ: Inspect entire output & exit code.
4. VERIFY: Does output prove the claim?
- If NO → report actual status with evidence
- If YES → state claim WITH evidence (command + summary)
5. ONLY THEN: Make the claim
Skipping any step = lying.
Common Claims & Required Evidence
| Claim | Required | Not Enough |
|---|---|---|
| “Tests pass” | Latest test command output showing 0 failures | Previous run, “should pass” |
| “Lint clean” | Linter command exit 0 now | Partial subset, inference |
| “Build works” | Build command exit 0 | Linter pass |
| “Bug fixed” | Reproduction test now passes | Code diff only |
| “Regression test exists” | Red→Green verified cycle | Test created but never failed |
| “Agent succeeded” | Inspect VCS diff + verify outputs | Agent success message |
Red Flags – STOP
- Saying “should/probably/seems”
- Expressing satisfaction before running verification
- Planning to commit/push/PR without a fresh run
- Trusting agent reports without checking
- Partial verification (“just ran affected tests”)
- “Just this once” or “I’m tired” rationalizations
Rationalization Rebuttals
| Excuse | Reality |
|---|---|
| “Should work now” | Run the command |
| “I’m confident” | Confidence ≠ evidence |
| “Just this once” | No exceptions |
| “Agent said success” | Verify independently |
| “Partial check is fine” | Partial proves nothing |
| “I’m exhausted” | Exhaustion isn’t evidence |
Patterns
- Tests: run and show
X/Y passingoutput. - Regression tests: demonstrate fail (red), apply fix, pass (green), revert to confirm failure if necessary.
- Requirements: re-read spec, create checklist, tick items with evidence.
- Agent work: inspect actual diff, run verification yourself.
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.
- 10d ago First seen · 75 lines · 28 tokens per session scan A 323b3035f627
eng-verification is a skill published in the GitHub repository tjboudreaux/cc-plugin-engineering-excellence (4 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 636 once invoked, about $0.0001 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
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.