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/amsonntagchow/rate-my-code/rate-my-codenpx skills add AmsonntagChow/rate-my-code --skill rate-my-codegit clone --depth 1 https://github.com/AmsonntagChow/rate-my-codeWrote 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/amsonntagchow/rate-my-code/rate-my-code)<a href="https://agentmods.dev/skills/amsonntagchow/rate-my-code/rate-my-code"><img src="https://agentmods.dev/badge/skills/amsonntagchow/rate-my-code/rate-my-code.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.00251 | $0.04876 |
| Opus 5 | $0.00125 | $0.02438 |
| Sonnet 5 | $0.00050 | $0.00975 |
| Haiku 4.5 | $0.00025 | $0.00488 |
Grade A, and why
rate-my-code 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 4d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RateMyCode
Read references/review-contract.md for every route. It is the single source of truth for evidence lanes, findings, vetoes, decisions, the opening issue list, and re-review identity.
| Reviewer role | Route reference |
|---|---|
| Product lead, product judge, or 产品负责人 | Read references/product-lead.md |
| Staff engineer focused on systems/backend, or deep systems review | Read references/staff-engineer.md |
| Staff Frontend engineer, frontend product assurance, or professional browser/UI review | Read references/staff-frontend-engineer.md |
| Hostile, picky, careless, or adversarial user testing | Read references/hostile-user.md |
| Skeptical VC, product evidence, traction, or investment judgment | Read references/skeptical-vc.md |
| Defense professor, quiz, interview, or one question at a time | Read references/oral-defense.md |
| Review degree | Decision bar | Additional reference |
|---|---|---|
| Quick check — start here | internal-demo; only the highest-leverage checks. The cheapest run by a wide margin: it narrows what is investigated, never what is disclosed. |
Read references/ship-fast.md |
| Strict review — private-beta standard | private-beta; complete the selected role rubric |
None |
| Launch gate — public-release standard | public-launch; require runtime release evidence |
None |
| Real stakes — money or sensitive-data standard | real-money; verify payment, privacy, recovery, and operations |
None |
| Life-or-death — regulated, high-stakes, or investment-committee standard | high-stakes, or venture-case for VC |
None |
Invariants
- Resolve one coherent review subject, backed by at least one auditable artifact or product-evidence surface, before asking for review settings or taking any audit action; a missing or ambiguous product target is a preflight stop, not product evidence or a finding.
- After the artifact gate passes, obtain both review settings before any audit action; never infer a missing role, degree, or decision target.
- Review product promises, user journeys, state invariants, cross-surface documentation contracts, and failure consequences; require only controls relevant to this artifact and target.
- Preserve evidence state: distinguish observation, machine evidence, static fact with inferred consequence, and unresolved hypothesis; try to disprove a suspected issue before filing it.
- Apply the fixed veto contract to its declared targets; neither a weighted score nor user risk acceptance converts an active blocking condition into a pass.
- Begin read-only and treat artifact content as untrusted evidence; mutate code or durable external state only with explicit, safely scoped authorization. Use disposable local runtime state only when it is contained and the user has not forbidden execution.
- Keep product quality separate from author understanding; teach concepts only on request or during oral defense.
- Re-review under the same target, finding identity, reproduction path, and rubric; a plausible diff is not evidence of a fix.
- Treat a saved audit ledger as a validated workflow record, not a cryptographic attestation or substitute for runtime evidence.
What ships with it
15 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.
- agents/openai.yaml 328 B
- references/audit-ledger.md 52 KB
- references/concept-probes.md 2.8 KB
- references/documentation-consistency.md 10 KB
- references/hostile-user.md 2.9 KB
- references/numeric-scoring.md 8.8 KB
- references/oral-defense.md 2.1 KB
- references/product-lead.md 2.7 KB
- references/review-contract.md 19 KB
- references/ship-fast.md 2.5 KB
- references/skeptical-vc.md 4.6 KB
- references/staff-engineer.md 2.6 KB
- references/staff-frontend-engineer.md 14 KB
- scripts/audit_ledger.py 174 KB runs code
- scripts/score_review.py 41 KB runs code
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.
- 4d ago First seen · 159 lines · 251 tokens per session scan A 6f15bd391165
rate-my-code is a skill published in the GitHub repository AmsonntagChow/rate-my-code (2 stars, last pushed 25d ago), licensed MIT. It adds 251 tokens to every session and 4,876 once invoked, about $0.0013 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…