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/fakoli/fakoli-plugins/verifynpx skills add fakoli/fakoli-plugins --skill verifygit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/verify)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/verify"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/verify.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.00017 | $0.02923 |
| Opus 5 | $0.00009 | $0.01461 |
| Sonnet 5 | $0.00003 | $0.00585 |
| Haiku 4.5 | $0.00002 | $0.00292 |
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 3d 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify (/fakoli-flow:verify)
Overview
Verification is not an opinion. It is a command you ran, output you read, and a result you can cite.
Core principle: Every PASS must cite fresh command output from this session. Every FAIL must cite what the output actually showed.
This skill is invoked:
- Automatically after
/fakoli-flow:executecompletes - Manually when the user runs
/fakoli-flow:verify - By
/fakoli-flow:quickafter the agent finishes
Step 1: Detect Project Language
Run the following to determine which verification commands apply:
# Check for language markers in order of specificity
[ -f tsconfig.json ] && echo "TypeScript"
[ -f Cargo.toml ] && echo "Rust"
{ [ -f pyproject.toml ] || [ -f setup.py ]; } && echo "Python"
| Marker file | Language |
|---|---|
tsconfig.json or package.json |
TypeScript |
Cargo.toml |
Rust |
pyproject.toml or setup.py |
Python |
If multiple markers exist, prefer the most specific: tsconfig.json > package.json.
If no marker is found: ask the user before proceeding.
Step 2: Run Language-Appropriate Checks
Run the full command for the detected language. Do not split it. Do not skip a step because the previous one passed.
TypeScript:
npx tsc --noEmit && bun test
Python:
ruff check . && mypy . && pytest
Rust:
cargo check && cargo test
Capture the full output of each command. Read exit codes. Count errors explicitly — do not skim.
Step 3: Dispatch Sentinel (if fakoli-crew is available)
If fakoli-crew is installed, dispatch the sentinel agent with the acceptance criteria from the plan.
How to find the plan:
ls docs/plans/ | sort | tail -1
Read the most recent plan file. Extract the acceptance criteria for each task (the **Acceptance criteria:** bullet points under each task heading).
If multiple plans exist for the current date: Do not guess. Ask the user:
Multiple plans found for today:
- docs/plans/2026-04-04-feature-a.md
- docs/plans/2026-04-04-feature-b.md
Which plan should I verify against?
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.
- 3d ago First seen · 321 lines · 17 tokens per session scan A b3ef2769949c
verify is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 25d ago), licensed MIT. It adds 17 tokens to every session and 2,923 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-31.
Other skills, from other repositories
better-auth-knowledge-patch
Use this skill when implementing, upgrading, debugging, or reviewing Better Auth applications. Start with the quick references below, then load the topic file that matches the task.
clickhouse-knowledge-patch
Use this skill when writing, reviewing, upgrading, or operating ClickHouse SQL and server configurations. Start with the compatibility-sensitive items below, then load the topic reference that matches the task.
arch-knowledge-patch
Restart the daemon immediately after upgrading openssh to 9.8p1 because the old daemon cannot accept new connections.
axum-knowledge-patch
Axum 0.8 uses return-position impl Trait in FromRequestParts and FromRequest. Implement their methods with native async fn; do not retain the old #[asynctrait] annotation.
caddy-knowledge-patch
Use this patch when writing or reviewing Caddyfile or JSON configuration, upgrading Caddy, building custom binaries, or operating Caddy's HTTP, proxy, certificate, and telemetry features.
cloudflare-d1-knowledge-patch
Use this skill when designing, implementing, migrating, operating, or debugging Cloudflare D1 databases. Check the project’s Wrangler configuration, binding usage, database generation, account plan, and remote-versus-local command flags before applying guidance.