Borrowing it
Nothing to install: this file belongs to talayash/agentrium. 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/talayash/agentrium/master/.claude/skills/verification-loop/SKILL.mdgit clone --depth 1 https://github.com/talayash/agentriumWrote 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/talayash/agentrium/verification-loop)<a href="https://agentmods.dev/skills/talayash/agentrium/verification-loop"><img src="https://agentmods.dev/badge/skills/talayash/agentrium/verification-loop/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/talayash/agentrium/verification-loop"><img src="https://agentmods.dev/badge/skills/talayash/agentrium/verification-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 41 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00014 | $0.00526 |
| Opus 5.5 | $0.00006 | $0.00210 |
| Sonnet 5.5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
verification-loop 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 1mo 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.
What it actually says
Verification Loop
A systematic verification pipeline that checks all aspects of project health before commits or releases.
When to Use
- Before committing significant changes
- Before creating a release
- After resolving merge conflicts
- When
/verifycommand is invoked
Pipeline Phases
Phase 1: Rust Backend Compilation
cd src-tauri && cargo check 2>&1
- Must compile with zero errors
- Warnings are acceptable but should be noted
Phase 2: Rust Linting
cd src-tauri && cargo clippy -- -W clippy::all 2>&1
- All clippy warnings should be addressed
#[allow(clippy::...)]only with justification
Phase 3: Rust Formatting
cd src-tauri && cargo fmt --check 2>&1
- Must pass with no formatting changes needed
Phase 4: TypeScript Type Check
npx tsc --noEmit 2>&1
- Zero type errors
- Strict mode compliance
Phase 5: Frontend Build
npm run build 2>&1
- Vite production build must succeed
- Check for bundle size warnings
Phase 6: IPC Contract Validation
- Every
#[tauri::command]incommands.rsregistered inmain.rs - Every
invoke()in frontend matches a registered command - Event names consistent between
emit()andlisten()
Phase 7: Security Quick Scan
- No
.unwrap()in production Rust code (use?or.map_err()) - No hardcoded secrets/tokens
- No
eval()orinnerHTMLin frontend - No
console.logwith sensitive data
Report Template
| Phase | Status | Duration | Notes |
|-------|--------|----------|-------|
| Rust compile | ✅/❌ | Xs | |
| Clippy | ✅/❌ | Xs | |
| Formatting | ✅/❌ | Xs | |
| TypeScript | ✅/❌ | Xs | |
| Vite build | ✅/❌ | Xs | |
| IPC contracts | ✅/❌ | - | |
| Security scan | ✅/❌ | - | |
**Result: PASS / FAIL**
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.
- 1mo ago Changed abb60d2fb503
- 1mo ago First seen · 79 lines · 14 tokens per session scan A 903e27e09be1
verification-loop is a skill published in the GitHub repository talayash/agentrium (46 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 526 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other skills, from other repositories
ratchet-files
Ratchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing. Use when a commit is blocked because a file is over the size budget, when asked to find or split…
github-review-pr
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
find-simplifications
Use when asked to find or plan Cherry Studio cleanup, simplification, refactoring, dead-code removal, duplicated state removal, unnecessary APIs, speculative generality, or library replacements, especially when the result should become evidence-backed proposed Agent Notes.
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…