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 agentmods add skills/sandsower/beislid/verifynpx skills add sandsower/beislid --skill verifygit clone --depth 1 https://github.com/sandsower/beislidWhat 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 | $0.00031 | $0.00589 |
| Opus 5 | $0.00015 | $0.00295 |
| Sonnet 5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
verify scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Identify** the verification command (test suite, linter, build, curl, etc.) How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Done
No completion claims without fresh verification evidence. Period.
If the repo declares custom lifecycle hooks, read ../lifecycle-hooks.md and honor any phase-boundary hooks before and after verify.
The Gate
When reporting durable evidence, use the terse Verification report shape from artifact-templates.md.
For every positive claim about work state:
- Identify the verification command (test suite, linter, build, curl, etc.)
- Run it fresh — not from memory, not from a previous run
- Read the actual output
- Confirm the output supports the claim
- Then make the claim
What Requires Evidence
| Claim | Required evidence |
|---|---|
| "Tests pass" | Test command output showing 0 failures |
| "Linter clean" | Linter output showing 0 errors |
| "Build succeeds" | Build command with exit code 0 |
| "Bug is fixed" | Failing test now passes (red to green) |
| "Feature works" | Test or manual verification output |
Proof Requirements
When a Work Contract includes proof_requirements, match verification evidence to that vocabulary before claiming done. A command log can satisfy command_gate, review output can satisfy review or fresh_eyes, CI status can satisfy ci_check, and a deck/screenshot can satisfy screenshot_show_me. Missing required proof means stop and report the missing proof or human interrupt; do not downgrade it to advisory in chat.
Red Flags
These words in your response without preceding evidence mean you're guessing:
- "should work", "probably works", "seems to be working"
- "I believe this fixes", "this should resolve"
- "tests should pass now"
Replace with: run the command, paste the output, state the fact.
After Subagent Work
Agent success reports are not evidence. After a subagent completes:
- Check the VCS diff
- Run verification independently
- Then confirm
What ships with it
1 file 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.
- 2d ago First seen · 61 lines · 31 tokens per session scan A 9762c473a6d0
verify is a skill published in the GitHub repository sandsower/beislid (10 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 589 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.