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 mickeyyaya/refactoring-skills --skill review-walkthroughsgit clone --depth 1 https://github.com/mickeyyaya/refactoring-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/mickeyyaya/refactoring-skills/review-walkthroughs)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/review-walkthroughs"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/review-walkthroughs/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/mickeyyaya/refactoring-skills/review-walkthroughs"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/review-walkthroughs.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.00069 | $0.05140 |
| Opus 5 | $0.00034 | $0.02570 |
| Sonnet 5 | $0.00014 | $0.01028 |
| Haiku 4.5 | $0.00007 | $0.00514 |
Grade A, and why
review-walkthroughs 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 9d 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 — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Walkthroughs
Overview
Each walkthrough follows the full review flow:
- Detect — identify the issue using the relevant skill (security, performance, language-specific)
- Calibrate — assign confidence level (C1–C4) and severity using
review-accuracy-calibration - Write feedback — apply the comment template from
review-feedback-quality - Decide — Request Changes, Approve with Comment, or Approve
Skills loaded in each scenario are listed explicitly. Use these walkthroughs to calibrate your own review process or to onboard reviewers to the full diagnostic flow.
Scenario Summary
| # | Language | Issue Type | Confidence | Severity | Verdict |
|---|---|---|---|---|---|
| 1 | Python | SQL Injection | C4 Certain | CRITICAL | Request Changes |
| 2 | Go | N+1 Query / performance | C3 High | HIGH | Request Changes |
| 3 | TypeScript | AI-generated: hallucinated API, stale closure, missing error handling | C3 High | HIGH | Request Changes |
| 4 | Java | Unsynchronized shared state / concurrency | C4 Certain | CRITICAL | Request Changes |
Scenario 1: Security Bug in Python Flask API
Context: A PR adds a /users/search endpoint to a Flask API. The endpoint accepts a query parameter and fetches matching users from a PostgreSQL database.
Skills loaded: security-patterns-code-review, review-accuracy-calibration, review-feedback-quality, python-review-patterns
Step 1: Detect
Scanning the endpoint handler for injection vectors — user input flows directly into a SQL string.
# Before: vulnerable endpoint
from flask import Flask, request
import psycopg2
app = Flask(__name__)
conn = psycopg2.connect("dbname=myapp user=postgres")
@app.route("/users/search")
def search_users():
query = request.args.get("q", "")
cursor = conn.cursor()
# VULNERABILITY: string interpolation in SQL
sql = f"SELECT id, name, email FROM users WHERE name LIKE '%{query}%'"
cursor.execute(sql)
rows = cursor.fetchall()
return {"users": [{"id": r[0], "name": r[1], "email": r[2]} for r in rows]}
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.
- 9d ago First seen · 531 lines · 0 tokens per session scan A 76c648794818
review-walkthroughs is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 69 tokens to every session and 5,140 once invoked, about $0.0003 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
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
vertical-hr-recruiting
Domain-knowledge primer for the HR & recruiting vertical (ATS, onboarding, workforce scheduling, engagement). Applied by architect/pm during spec authoring so they aren't naive about hiring pipelines, the admitted offer→onboard data-carry gap, EEO/I-9 compliance, and shift-coverage rules. Stops the four products from…
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…
vertical-retail
Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder…
vertical-fitness
Domain-knowledge pack for fitness & wellness (boutique studios, gyms, coaches, on-demand brands) — the membership vocabulary, non-obvious billing/booking rules, and retention realities a builder must know so fitness products aren't speced naive. Covers the four products this niche ships (class-booking, coaching…