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 Bilal140202/the-lord-of-the-skills --skill octaviantocan__agy-reviewgit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-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/bilal140202/the-lord-of-the-skills/octaviantocan__agy-review)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/octaviantocan__agy-review"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/octaviantocan__agy-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/bilal140202/the-lord-of-the-skills/octaviantocan__agy-review"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/octaviantocan__agy-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.00152 | $0.00939 |
| Opus 5.5 | $0.00061 | $0.00376 |
| Sonnet 5.5 | $0.00030 | $0.00188 |
| Haiku 4.5 | $0.00015 | $0.00094 |
Grade A, and why
agy-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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agy-review
Run anything past the agy CLI for a quick adversarial critique — questionable assumptions, flaws, risks, gaps, failure modes, and a SHIP/REVISE/RETHINK verdict — from a second, independent model. Use it to harden a thing before you commit to it, not to replace your own judgment.
It reviews whatever you give it — a plan or design is just one case. Also: a code change, an essay or doc, a product/architecture decision, an argument or pitch, a config, a prompt, a name, an idea. Raw code, numbered specs, prose — all fine.
What to review (arguments)
Invoked as /agy-review [text or file to review]. Interpret the argument — $ARGUMENTS — as what to critique:
- a file path → review its contents (pass it with
-f); - pasted text or an inline description → review that;
- nothing → review the most relevant artifact in the current context (e.g. the plan, draft, or decision you just produced), and state what you picked.
How to run it
One script does everything: scripts/agy-review.sh. Give it the content via stdin, a file, or an argument; add -c to say what the thing is so the critique is on-target.
# pipe content in (most common when reviewing your own draft)
printf '%s\n' "$THING" | scripts/agy-review.sh -
# from a file, with context about what it is / the goal
scripts/agy-review.sh -f design.md -c "B2B SaaS onboarding flow; must ship this sprint"
scripts/agy-review.sh -f rate-limiter.md -c "Node/Express service behind a load balancer"
It prints the critique to stdout and exits 0. Read the bullets, then weigh them — adopt the real ones, dismiss the off-base ones, and tell the user which is which.
Model
Defaults to Gemini 3.5 Flash (High) (Flash in its highest thinking mode), per preference. Override with AGY_REVIEW_MODEL="<name>" (see agy models for exact strings) or -m.
Reading the result
The last line is VERDICT: SHIP / REVISE / RETHINK - <biggest issue>. Treat it as input, not a verdict you must obey:
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 First seen · 59 lines · 152 tokens per session scan A 37ea3eeb2646
agy-review is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 152 tokens to every session and 939 once invoked, about $0.0006 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
first-plan-lens-engine
Skill que define o motor de detecção e roteamento de stack lenses do first-plan. Mapeia manifestos (go.mod, package.json, etc) -> stack -> papel -> lens skill correspondente. Use quando precisar decidir qual lens aplicar a uma pasta durante Discovery, ou quando estender suporte a uma nova stack.
first-plan-pattern-extraction
Skill que define como extrair padrões do código com confidence scoring. Use durante Discovery quando precisar identificar convenções, anti-padrões ou padrões idiomáticos do projeto. Cada padrão extraído deve vir com exemplo concreto do código (path:line).
serpsmith
Publish SEO articles, verify unattended health, and gate source-to-runtime releases.
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
coding-standards
Detects code smells, anti-patterns, and readability issues. Use when implementing features, reviewing code, or refactoring.
code-review-scope
Review a PR through the CodeReviewScope persona. Use when asked to check whether a PR stays within its intended scope, avoids crossing into unrelated topics, separates incidental cleanup from behavior changes, and keeps review lanes clear.