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 tony/skills --skill revisegit 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/revise)<a href="https://agentmods.dev/skills/tony/skills/revise"><img src="https://agentmods.dev/badge/skills/tony/skills/revise.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.1 | $0.00030 | $0.00696 |
| Opus 5 | $0.00015 | $0.00348 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
revise 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 4d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scholar:revise
Something the study asserted turned out to be wrong. This records that, rather than quietly making it true.
User arguments: $ARGUMENTS
Why a correction is kept
A RETRACTED CLAIM IS WORTH MORE WRITTEN DOWN THAN DELETED
Deleting it does not delete it from anyone's memory. A figure that circulated and turned out to measure something else keeps being repeated by everyone who read it before the fix, and they have no way to learn otherwise unless the study says so.
The correction also carries information the replacement does not: knowing that a plausible reading of the evidence was wrong tells the next reader which plausible readings to distrust.
Procedure
1. Establish what is being overturned
Usually from /scholar:verify (a citation that no longer says what it was
quoted as saying) or from /scholar:contest (a later round that killed an
earlier verdict). Take the claim as it currently stands, verbatim.
2. Append to evidence/corrections.md
## <the term or claim>
**Was:** the claim as it stood, quoted exactly.
**Rested on:** the citation or measurement that supported it.
**Failed because:** what overturned it, cited or measured.
**Now:** the replacement claim, or a statement that the question is open.
Append. Never rewrite an existing correction — a correction that was itself wrong gets its own entry beneath.
3. Update the study
Change the affected row in terms.jsonl and the affected evidence document,
then link the correction from the brief's section so a reader of the brief
meets it.
Rules
- Quote the old claim exactly. Paraphrasing a retraction is how a retraction becomes a second version of the original error.
- A correction states what overturned the claim, with the same evidence tier the claim itself required. "This turned out to be wrong" is not a correction.
- Where the replacement is "we do not know", say that. An open question is a legitimate resting state; a confident replacement invented to fill the hole is not.
- Never delete a correction to tidy the document.
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.
- 4d ago First seen · 89 lines · 30 tokens per session scan A 90e3eadd9a3a
revise is a skill published in the GitHub repository tony/skills (2 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 696 once invoked, about $0.0002 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-09-03.
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…
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…
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…
find-hypertable-candidates
Use this skill to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables. Trigger when user asks to: Analyze database tables for hypertable conversion potential Identify time-series or event tables in an existing schema Evaluate if a table would…