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 fivol/claude-make-better --skill meta-reviewgit clone --depth 1 https://github.com/fivol/claude-make-betterWrote 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/fivol/claude-make-better/meta-review)<a href="https://agentmods.dev/skills/fivol/claude-make-better/meta-review"><img src="https://agentmods.dev/badge/skills/fivol/claude-make-better/meta-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/fivol/claude-make-better/meta-review"><img src="https://agentmods.dev/badge/skills/fivol/claude-make-better/meta-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.00284 | $0.02791 |
| Opus 5 | $0.00142 | $0.01396 |
| Sonnet 5 | $0.00057 | $0.00558 |
| Haiku 4.5 | $0.00028 | $0.00279 |
Grade A, and why
meta-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 11d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
meta-review
Audit how the user and Claude Code have actually been working together — over a window of real session history — then turn that into a short, prioritized, actionable list and apply what the user picks. Each run is logged so the next run resumes from where this one stopped.
You are the orchestrator. The heavy, noisy reading of session logs happens inside subagents (one per lens) so this conversation's context stays clean and you keep only the findings. Do not read 60 session files yourself.
The data you're reviewing
Claude Code stores each session as a JSONL file under
~/.claude/projects/<encoded-cwd>/<session-id>.jsonl (the cwd's absolute path
with every non-alphanumeric char replaced by -). Records carry an ISO8601
timestamp and the cwd. Two ways to read this history:
- meta-cc MCP tools (preferred) — purpose-built aggregation over a project's
sessions, with
since/untiltime filters andjq_filter. Load them withToolSearch(querymeta-cc) since they're deferred. They default toscope: "project"(current project, all its sessions). Seereferences/meta-cc-queries.mdfor the call recipes per lens. - Raw JSONL (fallback) — if meta-cc is unavailable or broken (it's
hand-patched on this machine and occasionally breaks), read the session files
directly with
grep/jq. The helper'splanoutput lists the exact files.
Inputs (optional args)
Parse anything the user passed after the skill name; otherwise use defaults.
| Arg / phrase | Effect |
|---|---|
| (nothing) | Scope = current project. Window = since last review, else past 7 days. |
all / "all projects" / "везде" |
Scope = every project under ~/.claude/projects. |
<path> |
Scope = that project's cwd path. |
<N>d / "last N days" / "за N дней" |
Force window = past N days (ignore last-review date). |
since <DATE> / "с <дата>" |
Force window start. |
--default-days <N> |
Change the first-run default (otherwise 7). |
The log lives at .meta-review.jsonl in the cwd where the skill is invoked
(the project root), regardless of scope.
What ships with it
4 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.
- 11d ago First seen · 221 lines · 284 tokens per session scan A bc2e9d51b32e
meta-review is a skill published in the GitHub repository fivol/claude-make-better (5 stars, last pushed 1mo ago), licensed MIT. It adds 284 tokens to every session and 2,791 once invoked, about $0.0014 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…