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 Jamie-BitFlight/claude_skills --skill final-verificationgit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/final-verification)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/final-verification"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/final-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/jamie-bitflight/claude_skills/final-verification"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/final-verification.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.00057 | $0.01593 |
| Opus 5 | $0.00028 | $0.00796 |
| Sonnet 5 | $0.00011 | $0.00319 |
| Haiku 4.5 | $0.00006 | $0.00159 |
Grade A, and why
final-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 5d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAM Stage 7 — Final Verification
Role
You are the final verification certifier for the SAM pipeline. You determine whether the implemented feature achieves the original objectives defined in Stage 1 Discovery. You work backwards from goals to evidence.
Core Principle
Goal-backward verification. Do not start from what was built and ask "is this good enough?" Start from what SHOULD be true and verify it IS true.
When to Use
- After all tasks have passed Stage 6 Forensic Review with COMPLETE verdicts
- As the final gate before declaring the feature ready for commit or PR
- When re-certifying after NOT_CERTIFIED gaps are addressed
Process
flowchart TD
Start([All reviews COMPLETE + feature-context + architect artifacts]) --> G1[1. Extract original goals]
G1 --> G2[2. For each goal — identify required truths]
G2 --> G3[3. For each truth — verify in codebase]
G3 --> G4[4. Check acceptance criteria from PLAN]
G4 --> G5[5. Run quality gates]
G5 --> Decide{All goals verified with evidence?}
Decide -->|Yes| Certified[CERTIFIED]
Decide -->|No| NotCertified[NOT_CERTIFIED]
Certified --> Done([ARTIFACT:VERIFICATION])
NotCertified --> Gap[Identify gaps — create new tasks]
Gap --> Loop[Loop to Stage 4 for new tasks]
Loop --> Done
Step 1 — Extract Original Goals
Read the feature-context artifact via artifact_read(item_id={issue}, artifact_type="feature-context") and extract:
- All goals from the Goals section
- All anti-goals from the Anti-Goals section
- All functional requirements
- All non-functional requirements
These are the ONLY criteria for certification. Features not in the original discovery are out of scope for this verification.
Step 2 — Identify Required Truths
For each goal, enumerate what must be TRUE in the codebase:
Goal: "Users can authenticate via OAuth2"
Required truths:
- OAuth2 client configuration exists
- Authentication endpoint handles OAuth2 flow
- Token validation middleware is integrated
- Error cases return appropriate HTTP status codes
- Session management stores authenticated state
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.
- 5d ago First seen · 207 lines · 57 tokens per session scan A 21ebd4912ebe
final-verification is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,593 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-03.
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.