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 agentmods add skills/tykisgod/quick-question/self-reviewnpx skills add tykisgod/quick-question --skill self-reviewgit clone --depth 1 https://github.com/tykisgod/quick-questionWrote 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/tykisgod/quick-question/self-review)<a href="https://agentmods.dev/skills/tykisgod/quick-question/self-review"><img src="https://agentmods.dev/badge/skills/tykisgod/quick-question/self-review.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 | $0.00024 | $0.00725 |
| Opus 5 | $0.00012 | $0.00362 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
self-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 5d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Review changes from the most recent interaction via a subagent review loop. Automatically loops until no critical issues remain or 5 rounds are completed.
For Unity changes: when verifying that a runtime/scene change actually behaves as intended, use tykit live queries (
unity_query/get-field/console) instead of re-reading the diff. Seeshared/tykit-first.md.
Steps
1. Collect changed files
Look back at the files changed in the most recent interaction and list them (file paths + one-line summary of each change).
2-6. Automated Review Loop
Loop automatically. Terminates when:
- No
[Critical]issues in the review - 5 rounds completed
- No new critical issues in two consecutive rounds
Output === Round N/5 === at the start of each round.
a. Dispatch review subagent
Dispatch a subagent (subagent_type: "general-purpose", model: "opus") with a prompt containing:
- The list of changed files and a summary of what was changed
- The full current content of each changed file (read them yourself first, then paste into the prompt — the subagent cannot read your session history)
- Review checklist:
- Logical correctness — are references correct, are step numbers sequential, do file paths exist
- Consistency — does the style match existing content in this repo
- Omissions — are there related files that should have been updated but were missed
- Redundancy — unnecessary blank lines, duplicate content
- Naming — are renamed symbols/paths consistent everywhere
- Required output format: classify each finding as
[Critical],[Moderate], or[Suggestion]with file path, line number, and explanation
b. Fix confirmed issues
- For each
[Critical]issue: fix immediately - For each
[Moderate]issue: fix at discretion [Suggestion]items: note but do not fix unless trivial
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.
- 5d ago First seen · 68 lines · 24 tokens per session scan A 1d95349fb955
self-review is a skill published in the GitHub repository tykisgod/quick-question (11 stars, last pushed 10d ago), licensed MIT. It adds 24 tokens to every session and 725 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-08-30.
Other skills, from other repositories
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.