Borrowing it
Nothing to install: this file belongs to getlien/lien. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/getlien/lien/main/.claude/skills/review/SKILL.mdgit clone --depth 1 https://github.com/getlien/lienWrote 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/getlien/lien/review)<a href="https://agentmods.dev/skills/getlien/lien/review"><img src="https://agentmods.dev/badge/skills/getlien/lien/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/getlien/lien/review"><img src="https://agentmods.dev/badge/skills/getlien/lien/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.00052 | $0.04035 |
| Opus 5.5 | $0.00021 | $0.01614 |
| Sonnet 5.5 | $0.00010 | $0.00807 |
| Haiku 4.5 | $0.00005 | $0.00404 |
Grade A, and why
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 1mo 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago Changed · +7 lines bc0fa46c1176
- 1mo ago First seen · 325 lines · 52 tokens per session scan A 712578ff43c9
review is a skill published in the GitHub repository getlien/lien (2 stars, last pushed 1mo ago), licensed AGPL-3.0. It adds 52 tokens to every session and 4,035 once invoked, about $0.0002 per session on Opus 5.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
paparats-search
Use when answering a question about code in the user's indexed repositories — where something is implemented, how a flow works, who calls a function, or what a change would affect. Explains when to use Paparats semantic search and when a text search is the better tool.
review-changes
Review current staged, unstaged, and untracked Git changes for correctness and regression risk, grounded in changed paths, diffs, focused file reads, and nearby test discovery. Use when the user asks to review local changes or a working-tree diff; do not use for broad repository audits.
karpathy-guidelines
Surgical execution guardrails for coding, debugging, review, and refactor tasks.
code-review
Review diffs and change sets for bugs, regressions, risks, and missing tests.
code-review
Performs structured code review on a file or directory.
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…