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 vertti/se-cove-claude-plugin --skill auto-verifygit clone --depth 1 https://github.com/vertti/se-cove-claude-pluginWrote 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/vertti/se-cove-claude-plugin/auto-verify)<a href="https://agentmods.dev/skills/vertti/se-cove-claude-plugin/auto-verify"><img src="https://agentmods.dev/badge/skills/vertti/se-cove-claude-plugin/auto-verify/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/vertti/se-cove-claude-plugin/auto-verify"><img src="https://agentmods.dev/badge/skills/vertti/se-cove-claude-plugin/auto-verify.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.00000 | $0.00637 |
| Opus 5 | $0.00000 | $0.00318 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
auto-verify 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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Verify Skill (Software Engineering)
This skill suggests using /verify for software engineering tasks that would benefit from systematic verification.
Design Philosophy
Be minimal and non-eager. Users invoke /verify when they want it. This skill only suggests verification in specific high-value scenarios where the user might not realize verification would help.
When to Suggest Verification
Only suggest /verify when the user's question involves ALL of these:
- Significant complexity - Not a trivial fix or simple question
- High risk of subtle bugs - Async patterns, state management, security
- Verifiable claims - There are specific behaviors that can be tested
Good Candidates
Complex code patterns with known pitfalls:
- React hooks with async behavior (useEffect, useCallback + async)
- Debouncing/throttling implementations
- Race condition scenarios
- Caching strategies
- Authentication/authorization flows
Security-sensitive operations:
- Input validation and sanitization
- Token handling and session management
- Password hashing and credential storage
- Encryption/decryption implementations
- Access control and permission checks
Complex async patterns:
- Promise chains with error handling
- Concurrent operations with shared state
- Retry logic with backoff strategies
- Streaming and chunked data processing
- WebSocket or real-time connection handling
Financial and critical operations:
- Payment processing logic
- Inventory or balance calculations
- Audit logging implementations
- Data migration scripts
- Rate limiting implementations
Architectural decisions with significant tradeoffs:
- State management approach (Redux vs alternatives)
- Microservices vs monolith
- Database schema design
- API design patterns
Bug investigations where the cause is uncertain:
- "I think the bug is X but not sure"
- Intermittent failures
- Production issues with incomplete information
When NOT to Suggest
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.
- 9d ago First seen · 88 lines · 0 tokens per session scan A 983bc6b5a793
auto-verify is a skill published in the GitHub repository vertti/se-cove-claude-plugin (20 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 637 tokens. 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
logic-review
Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…
logic-fix-all
Autonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free. Trigger when the user wants ALL logic issues found and fixed — "fix everything", "fix all logic…
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…
run-iteration-eval
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first. Use when the user wants to "run the…
new-skill
Scaffold a new logic- skill in the Logic-Lens repo and wire it into every place a skill must be registered, so no step is missed. Use when adding a seventh (or later) skill to Logic-Lens.
sync-skill-cache
Sync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills//SKILL.md or guide/shared file and BEFORE running content-evals — otherwise the eval silently grades stale content and every token is…