Borrowing it
Nothing to install: this file belongs to aemsites/author-kit. 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/aemsites/author-kit/main/.agents/skills/performance-review/SKILL.mdgit clone --depth 1 https://github.com/aemsites/author-kitWrote 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/aemsites/author-kit/performance-review)<a href="https://agentmods.dev/skills/aemsites/author-kit/performance-review"><img src="https://agentmods.dev/badge/skills/aemsites/author-kit/performance-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/aemsites/author-kit/performance-review"><img src="https://agentmods.dev/badge/skills/aemsites/author-kit/performance-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.00067 | $0.02331 |
| Opus 5.5 | $0.00027 | $0.00932 |
| Sonnet 5.5 | $0.00013 | $0.00466 |
| Haiku 4.5 | $0.00007 | $0.00233 |
Grade A, and why
performance-review scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const data = fetch(url).then((r) => r.json()); // started, not awaited How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance review
This project is buildless and every line ships. Regressions here are not slow functions — they are bytes and requests added before first paint, and work hoisted ahead of the lifecycle stage that should own it.
This skill analyzes; it does not measure. Lighthouse against a proxied dev server produces numbers that are not the published numbers, and every check below is decidable from source.
Report findings. Do not fix them unless asked.
The lifecycle — what already happens, in order
| # | Where | What runs | Network |
|---|---|---|---|
| 1 | scripts.js top level |
setConfig, then top-level await loadPage() |
no |
| 2 | loadArea → decorateSession / decorateDoc (document only) |
header mode, template metadata, stored color scheme, hash → localStorage |
no |
| 3 | decoratePictures |
adds the 3000px source to picture:has([loading]) |
no |
| 4 | config.decorateArea hook |
project-specific; today eager-loads the first image | no |
| 5 | decorateSections |
.section wrapping, child regrouping, decorateLinks |
no |
| 6 | section loop, per section | loadIcons, then link blocks, then div blocks, then section-metadata |
yes — dynamic import per block, parallel within a phase, sections awaited in order |
| 7 | after section 0 | postlcp.js (loads the header block), deps/rum.js |
deferred |
| 8 | after all sections | lazy.js → lazyhash, favicon, footer, author tools in non-prod |
deferred, post-paint |
Steps 1–5 are synchronous and block the first section. Anything added there delays every paint on every page.
Parallelize with purpose
Awaited and unawaited async are both deliberate here. The pattern is consistent once you see it:
- The LCP image and the first section's blocks race — same paint, so concurrency costs nothing and finishing sooner helps.
- Blocks within a section run concurrently — all of them are needed for that section to render.
- Sections are awaited one at a time — section 3's blocks racing section 0's would saturate bandwidth and delay LCP for content nobody can see yet.
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 · +1 tokens per session e05b99d4bf7c
- 2mo ago First seen · 188 lines · 66 tokens per session scan A 54b2110c0273
performance-review is a skill published in the GitHub repository aemsites/author-kit (12 stars, last pushed 29d ago), licensed Apache-2.0. It adds 67 tokens to every session and 2,331 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…