Borrowing it
Nothing to install: this file belongs to sflandergan/agentic-coding. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sflandergan/agentic-coding/main/.agents/skills/agent-verification/SKILL.mdgit clone --depth 1 https://github.com/sflandergan/agentic-codingWrote 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/sflandergan/agentic-coding/agent-verification)<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/agent-verification"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/agent-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/sflandergan/agentic-coding/agent-verification"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/agent-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.00025 | $0.00671 |
| Opus 5.5 | $0.00010 | $0.00268 |
| Sonnet 5.5 | $0.00005 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade D, and why
agent-verification scanned grade D with 2 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 2mo 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -la .claude/skills/ # each should point to ../../.agents/skills/<name> Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .temp/smoke-test .temp/smoke-copy How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Verification — Self-Maintenance
Core principle: Evidence before claims, always. If you haven't run the verification command, you cannot claim it passes.
The Gate
BEFORE claiming any status:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code
4. VERIFY: Does output confirm the claim?
5. ONLY THEN: Make the claim (with evidence)
Verification Commands
For bash scripts (scripts/init.sh, scripts/copy.sh)
shellcheck scripts/init.sh scripts/copy.sh
bash -n scripts/init.sh
bash -n scripts/copy.sh
Smoke run (scripts)
Run the script against a throwaway target dir under .temp/:
mkdir -p .temp/smoke-test
echo -e "1\n1\n.temp/smoke-test/target" | bash scripts/init.sh
For copy.sh:
mkdir -p .temp/smoke-copy && cd .temp/smoke-copy && git init && echo "placeholder" > README.md && git add . && git commit -m "init"
cd ../..
echo -e "1\n1" | bash scripts/copy.sh .temp/smoke-copy
Clean up after:
rm -rf .temp/smoke-test .temp/smoke-copy
For markdown files
No compilation check, but verify:
- SKILL.md frontmatter has required
nameanddescription - Agent
.mdfiles have requireddescriptionin frontmatter - Run
codespellon changed markdown, agent, skill, README, and prose-heavy script files - No broken relative links (manual spot-check)
codespell README.md .agents/skills/agent-planning/SKILL.md
Scope codespell to changed files by default. Run it more broadly when a plan explicitly calls for repo-wide spelling validation.
Consistency checks
# README lists match actual files
ls .opencode/agents/ # should match README's agent list
ls .agents/skills/ # should match README's skill list
# Lockfiles match their distinct scopes
jq '.skills | keys' skills-lock.json
jq '.skills | keys' core/skills-lock.json
# Symlinks resolve
ls -la .claude/skills/ # each should point to ../../.agents/skills/<name>
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.
- 2mo ago First seen · 102 lines · 25 tokens per session scan D 4e18a599ad97
agent-verification is a skill published in the GitHub repository sflandergan/agentic-coding (4 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 671 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 2 findings (enumerates other installed skills, recursive force delete). 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".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
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.