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 jmylchreest/aide --skill verifygit clone --depth 1 https://github.com/jmylchreest/aideWrote 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/jmylchreest/aide/verify)<a href="https://agentmods.dev/skills/jmylchreest/aide/verify"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/verify.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 48 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]
- medium MCP Rug Pull · line 131 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.00010 | $0.01557 |
| Opus 5 | $0.00005 | $0.00779 |
| Sonnet 5 | $0.00002 | $0.00311 |
| Haiku 4.5 | $0.00001 | $0.00156 |
Grade A, and why
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 8d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Mode
Recommended model tier: smart (opus) - this skill requires complex reasoning
Active QA verification: run all quality checks and report pass/fail status.
Purpose
This is the VERIFY stage of the SDLC pipeline. Implementation is complete. Your job is to run comprehensive validation and report results.
This is different from review: Review is read-only analysis. Verify is active execution of quality checks.
Verification Checklist
Run ALL of the following. Each must pass.
1. Full Test Suite
# TypeScript/JavaScript
npm test
# Go
go test ./...
# Python
pytest
Expected: All tests pass, no failures, no skipped tests.
2. Type Checking
# TypeScript
npx tsc --noEmit
# Go (implicit in build)
go build ./...
# Python (if using mypy)
mypy .
Expected: No type errors.
3. Linting
# TypeScript/JavaScript
npm run lint
# Go
go vet ./...
golangci-lint run
# Python
ruff check .
Expected: No lint errors. Warnings acceptable if pre-existing.
4. Build
# TypeScript/JavaScript
npm run build
# Go
go build ./...
# Python
python -m py_compile *.py
Expected: Build succeeds without errors.
5. Debug Artifact Check
Search for common debug artifacts that shouldn't be committed:
# Console logs (JS/TS)
Grep for "console.log" in changed files
# Debug prints (Go)
Grep for "fmt.Println" or "log.Print" that look like debug
# Python debug
Grep for "print(" or "pdb" or "breakpoint()"
# TODO/FIXME comments
Grep for "TODO" or "FIXME" in changed files
# Debugger statements
Grep for "debugger" in JS/TS files
Expected: No debug artifacts in new code. Pre-existing ones noted but not blocking.
6. Uncommitted Changes Check
git status
Expected: Working directory clean, or only expected files modified.
Workflow
Step 1: Run All Checks
Execute each check in sequence, capturing output:
# Run all checks, capture results
npm test 2>&1 | head -50
npm run lint 2>&1 | head -50
npx tsc --noEmit 2>&1 | head -50
npm run build 2>&1 | head -50
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.
- 8d ago First seen · 300 lines · 10 tokens per session scan A 94766fcb7bd1
verify is a skill published in the GitHub repository jmylchreest/aide (16 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 1,557 once invoked, about $0.0001 per session on Opus 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
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
tmux-real-user-testing
A real-user test workflow for Qwen Code's terminal interface, using tmux to drive the program and capture readable screen snapshots. tmux is a tool for running and observing terminal sessions.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
deflake
Stabilize a flaky test with a minimal, assertion-preserving fix — never by weakening or deleting the check.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.