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/tony/skills/verifynpx skills add tony/skills --skill verifygit clone --depth 1 https://github.com/tony/skillsWrote 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/tony/skills/verify)<a href="https://agentmods.dev/skills/tony/skills/verify"><img src="https://agentmods.dev/badge/skills/tony/skills/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.00030 | $0.00759 |
| Opus 5 | $0.00015 | $0.00380 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
verify 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 yesterday.
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.
$ curl -s -o /dev/null -w '%{http_code}\n' -L '<url>' This is a copy
88% identical to scholar-verify — 29 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scholar:verify
A study is a set of claims about a corpus that keeps moving. Without this, it rots into confident falsehood: every link still resolves, every number still reads as measured, and none of it is true any more.
Read ../../references/citation.md for what a citation was required to carry.
User arguments: $ARGUMENTS
Procedure
1. Walk every citation
For each cites entry in terms.jsonl, confirm three things separately,
because they fail differently:
The ref still exists. A tag can be moved or deleted, and a deleted tag makes every URL built on it a 404 rather than a wrong answer.
The file still exists at that path on that ref.
$ curl -s -o /dev/null -w '%{http_code}\n' -L '<url>'
The quoted text still appears at the recorded locator. This is the one that fails silently: a file that grew by ten lines leaves a line-anchor citation resolving to unrelated code while still returning 200.
2. Re-run the measurements
With --refresh-metrics, run every command recorded in evidence/metrics.md
and diff the output against what was recorded. A number that changed is not
automatically wrong — the corpus moved — but it is no longer evidence for the
claim it was cited under.
3. Report by failure mode
Four categories, because the remedy differs:
- Moved — the ref advanced or the tag was retargeted. Re-pin.
- Vanished — the file or ref is gone. The claim needs a new source or it needs retracting.
- Misquoted — the locator resolves but the text there is not what was quoted. This is the dangerous one, and it is why quotations are recorded rather than just links.
- Changed — a measurement produced a different number.
Rules
- Do not edit a claim in place. Anything that overturns a standing claim goes
to
/scholar:revise, which records what was believed and why it failed. - Report a broken citation; do not repair it by finding a new source that happens to support the same claim. That is fitting evidence to a conclusion.
- A citation that cannot be checked — a source now behind a paywall, a deleted repository — is reported as uncheckable, not as passing.
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.
- yesterday First seen · 82 lines · 30 tokens per session scan A bcc32178c5bb
verify is a skill published in the GitHub repository tony/skills (2 stars, last pushed 6d ago), licensed MIT. It adds 30 tokens to every session and 759 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 88% identical to scholar-verify, differing in 29 lines, and is treated as a copy.
Other skills, from other repositories
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
design-postgis-tables
Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications.
migrate-postgres-tables-to-hypertables
Use this skill to migrate identified PostgreSQL tables to Timescale/TimescaleDB hypertables with optimal configuration and validation. Trigger when user asks to: Migrate or convert PostgreSQL tables to hypertables Execute hypertable migration with minimal downtime Plan blue-green migration for large tables Validate…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
postgres-hybrid-text-search
Use this skill to implement hybrid search combining BM25 keyword search with semantic vector search using Reciprocal Rank Fusion (RRF). Trigger when user asks to: Combine keyword and semantic search Implement hybrid search or multi-modal retrieval Use BM25/pgtextsearch with pgvector together Implement RRF (Reciprocal…