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/abuango/pos-ai/verificationnpx skills add abuango/pos-ai --skill verificationgit clone --depth 1 https://github.com/abuango/pos-aiWrote 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/abuango/pos-ai/verification)<a href="https://agentmods.dev/skills/abuango/pos-ai/verification"><img src="https://agentmods.dev/badge/skills/abuango/pos-ai/verification.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00593 |
| Opus 5 | $0.00019 | $0.00296 |
| Sonnet 5 | $0.00008 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
verification 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 4d 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.
2. Health endpoint: `curl -s -o /dev/null -w "%{http_code}" https://{url}/health` How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Verification
Run verification checklist to confirm work is actually complete. Never trust output alone.
Setup
Before starting: check .handoff/sessions/ for active sessions, read context status.yaml, run git status. Follow .rules/universal.md (Plan -> Approve -> Execute).
Commands
/verify task {files...}- Verify task completion/verify deploy {team} {service}- Verify deployment/verify pr- Verify PR readiness/verify tests {path}- Verify tests pass
Core Principle
Agent outputs can describe work without actually performing it. Verification is mandatory.
/verify task {files...}
- File existence:
ls -la {files} - File content: Read each file, check syntax, logic, no placeholder TODOs
- Git status:
git status && git diff --stat— verify changes match claims - Run tests:
php artisan test/npm test/go test/flutter test - Report: Files verified table, test results, git status, VERIFIED/NOT VERIFIED
/verify deploy {team} {service}
- Check deployment platform status (via MCP if configured)
- Health endpoint:
curl -s -o /dev/null -w "%{http_code}" https://{url}/health - Check logs for startup errors / exceptions
- Version verification:
curl https://{url}/api/version
/verify pr
- Branch status:
git log origin/main..HEAD --oneline - Run tests
- Run linting
- Check for debug code:
grep -r "console.log\|debugger\|dd(\|dump(" .
Red Flags
- Perfect metrics (100% pass, 95%+ coverage) — suspicious
- Rapid completion of complex work
- Detailed docs without evidence
- No error mentions — real work always has hiccups
Enforcement
No verification = No completion. Status should only show complete after files verified, tests run and passing, git status reviewed.
Full SOP: docs/system/sops/verification-protocol.md
Self-Assessment (Internal)
Rate this skill execution 0-10. If < 8, write feedback to .handoff/feedback/{date}-{skill-name}.yaml with: skill, rating, friction, suggestion, context. Do not mention to user.
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.
- 4d ago First seen · 64 lines · 38 tokens per session scan A 0b56fb08e42c
verification is a skill published in the GitHub repository abuango/pos-ai (2 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 593 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…