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 Mathews-Tom/armory --skill surrogate-verifiergit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/mathews-tom/armory/surrogate-verifier)<a href="https://agentmods.dev/skills/mathews-tom/armory/surrogate-verifier"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/surrogate-verifier.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.00056 | $0.01887 |
| Opus 5 | $0.00028 | $0.00944 |
| Sonnet 5 | $0.00011 | $0.00377 |
| Haiku 4.5 | $0.00006 | $0.00189 |
Grade A, and why
surrogate-verifier 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 3d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Surrogate Verifier
Generate structured test assertions and failure diagnostics for skill packages through information-isolated verification. The verifier operates without access to the skill generator's reasoning — it sees only the skill definition, a task prompt, and the output artifacts. This isolation prevents confirmation bias and is the single largest contributor to skill quality in co-evolutionary generation (+30pp per EvoSkills).
Reference Files
| File | Contents | Load When |
|---|---|---|
references/assertion-patterns.md |
Assertion catalog by skill category with weight guidance | Always |
references/diagnostic-templates.md |
Failure diagnostic templates with root-cause categories | When producing failure reports |
Information Isolation Protocol
This is the most critical constraint. Violating isolation degrades verification quality.
The verifier MUST NOT access:
- The generator's conversation history or reasoning chain
- Prior evolution iterations or refinement context
- The generator's internal notes or decision rationale
- Any context beyond what is explicitly listed below
The verifier receives ONLY:
- The skill's
SKILL.mdcontent (the definition file) - One or more task prompts representing intended use
- The skill's output (when diagnosing failures)
- The assertion results from
scripts/eval_assertions.py(when diagnosing)
Implementation: When invoked by the test-engineer agent, this skill MUST be loaded
into a separate Agent spawn using isolation: "worktree" or at minimum a fresh session
with no shared context. The invoking agent passes artifacts as explicit text, not as
conversation references.
Workflow
Mode 1: Assertion Generation
What ships with it
3 files 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.
- 3d ago First seen · 197 lines · 56 tokens per session scan A 33a2253b985e
surrogate-verifier is a skill published in the GitHub repository Mathews-Tom/armory (316 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,887 once invoked, about $0.0003 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
implement
Execute approved Hardproof tasks during IMPLEMENT with focused tests, durable task updates, and scope-controlled code changes.
review
Challenge a Hardproof implementation during REVIEW against its approved contract, code quality, tests, and risk boundaries.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
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.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.