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 weave-reviewgit 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/weave-review)<a href="https://agentmods.dev/skills/tony/skills/weave-review"><img src="https://agentmods.dev/badge/skills/tony/skills/weave-review/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/tony/skills/weave-review"><img src="https://agentmods.dev/badge/skills/tony/skills/weave-review.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.00021 | $0.10555 |
| Opus 5 | $0.00010 | $0.05278 |
| Sonnet 5 | $0.00004 | $0.02111 |
| Haiku 4.5 | $0.00002 | $0.01056 |
Grade A, and why
weave-review 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 7d 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 — 846 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weave Code Review
Run code review through independent adversarial workers in parallel, then synthesize their findings into a unified report with evidence-backed adjudication. Host-native sub-agents are the default; separate model CLIs are optional. This is a project-read-only command — no files in your repository are written, edited, or deleted. Session artifacts (worker outputs, prompts, synthesis results) are persisted to $AI_AIP_ROOT for post-session inspection; this directory is outside your repository.
Worker selection
Before any other unresolved configuration choice or operational step, read
references/worker-backends.md. Resolve
worker_backend from --workers=subagents|model-clis using that reference;
if the flag is absent, ask its worker question first.
If interactive choice is unavailable, honor its documented headless default.
The selected backend governs the whole session: dispatch, retry, judging, refinement, artifacts, session metadata, and presentation. The shared reference adapts provider-named examples across every later phase to that backend.
When worker_backend == subagents, use only the reference's native sub-agent
path. Skip every model-CLI detection, timeout question, timeout resolution,
retry, fallback, and dispatch instruction below. Every such instruction below
is conditional on worker_backend == model-clis.
Orchestration Plan
Before dispatching the review to models, enter plan mode to create a review strategy.
Enter your tool's plan mode:
- Claude Code: Call
EnterPlanMode - Cursor: Use
/planor pressShift+Tab - Codex: Use
/planto switch to Plan mode - Gemini: Use
/planor pressShift+Tab - Other tools: Use your tool's planning/read-only mode if available
If plan mode is not available, proceed — context gathering in Phase 1 still guides the review.
Create an orchestration plan covering:
- Branch summary — What does this branch do? Summarize from commit messages and diff stats
- Review focus areas — Which files/changes are highest risk or most complex? Where should reviewers concentrate?
- Relevant conventions — Which CLAUDE.md/AGENTS.md rules are most relevant to the changes in this branch?
- Known concerns — Any areas the user flagged, or patterns in the diff that look risky (large functions, missing tests, API changes)
- Model prompt strategy — What specific instructions should each model's review prompt emphasize, given the above?
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 846 lines · 21 tokens per session scan A 5b22477a078c
weave-review is a skill published in the GitHub repository tony/skills (2 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 10,555 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-09-03.
Other skills, from other repositories
code-reviewer
Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code…
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.
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…