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 dhaupin/vant --skill vant-skill-review-performancegit clone --depth 1 https://github.com/dhaupin/vantWrote 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/dhaupin/vant/vant-skill-review-performance)<a href="https://agentmods.dev/skills/dhaupin/vant/vant-skill-review-performance"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-review-performance.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.1 | $0.00007 | $0.00490 |
| Opus 5 | $0.00003 | $0.00245 |
| Sonnet 5 | $0.00001 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
review-performance 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 8d 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.
curl -s -o /dev/null -w "%{size_download}" URL What it actually says
Performance Review
Is it fast?
Rule #1
Measure. Don't guess.
# Profile before you optimize
node --prof app.js
What To Check
1. Time
// Time operations
const start = Date.now()
doThing()
console.log(Date.now() - start)
| Check | Target |
|---|---|
| API < 200ms | |
| Page < 1s | |
| Build < 30s |
2. Network
# Check size
curl -s -o /dev/null -w "%{size_download}" URL
| Size | Rating |
|---|---|
| > 1MB | SLOW |
| > 500KB | MEDIUM |
| < 100KB | FAST |
3. Queries
// N+1 query?
items.map(i => db.get(i.id))
| Pattern | Issue | Fix |
|---|---|---|
| query in loop | N+1 | Batch |
| select * | Too much | Select needed |
| no cache | Repeat | Cache |
4. Async
// Blocking?
await heavy()
await more()
| Pattern | Issue | Fix |
|---|---|---|
| Sequential | Slow | Promise.all |
| No timeout | Hang | Timeout |
| No limit | OOM | Limit |
Output
## Performance - [endpoint]
### Timing
- [TIME] [endpoint]: [ms]ms
- Target: [target]ms
### Network
- [SIZE] [kb]kb
### Queries
- [COUNT] queries for [records]
- Issue: [pattern]
### Recommendations
1. [fix 1]
2. [fix 2]
Fix Priority
| Priority | When |
|---|---|
| 1 | Blocks user |
| 2 | Noticeable delay |
| 3 | Optimization |
Role: Performance Reviewer
Input: Code or endpoint
Output: Is fast?
Measure it. Fix what matters.
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.
- 8d ago First seen · 124 lines · 7 tokens per session scan A f3d8584df684
review-performance is a skill published in the GitHub repository dhaupin/vant (9 stars, last pushed 8d ago), licensed MIT. It adds 7 tokens to every session and 490 once invoked, about $0.0000 per session on Opus 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-31.
Other skills, from other repositories
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.
rn-debugging
This skill should be used when the user asks to "debug the app", "fix a crash", "diagnose a blank screen", "read error logs", "troubleshoot CDP connection", "check Metro status", "find native crashes", "inspect network failures", "the app crashed", "I see a blank screen", "the screen is white", "something broke", "app…
doctor
Explicit Codex workflow: Run strictly read-only Codex plugin, MCP contract, schema, and environment diagnostics; recommend but never execute recovery.
debug-screen
Explicit Codex workflow: Diagnose why the current screen is broken, showing unexpected content, or crashing. Gathers parallel evidence from all layers and applies a targeted fix.
performance-optimization
Measure-first performance work. Use on triggers like "it's slow", "profile this", "optimize perf", "fix the bottleneck", "improve load time / Core Web Vitals", or when a measured regression needs fixing. Enforces measure-before-optimize. Fills a perf gap not covered by existing project skills. Not a build/ship…
ci-troubleshoot
Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 10-file workflow taxonomy, the release pipeline, known failure modes, and how to read gh run logs and retrigger jobs. Use when a CI run is red, a release is stuck, a workflow won't dispatch, or you need to know which workflow does what. See release-cut to…