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 jamestorrevillas/dev-skills --skill performance-reviewgit clone --depth 1 https://github.com/jamestorrevillas/dev-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/jamestorrevillas/dev-skills/performance-review)<a href="https://agentmods.dev/skills/jamestorrevillas/dev-skills/performance-review"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/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/jamestorrevillas/dev-skills/performance-review"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/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.00059 | $0.00545 |
| Opus 5 | $0.00030 | $0.00272 |
| Sonnet 5 | $0.00012 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
performance-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 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.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Review Writing
Core Principles
- Write only what you actually did — no inflation, no filler phrases
- Use "Assisted in..." when not the primary contributor
- Quantify where possible: coverage %, stories completed, time reduced
- Never use: "demonstrating strong commitment to...", "showcasing my passion for..."
- For peer feedback with limited collaboration: keep general, honest, safe
Self-Assessment Format
Accomplishment Writing Pattern
WEAK: "Worked on the BTT module"
STRONG: "Built Query Clarity Assessment Agent (US-2111704),
achieving 95%+ unit and integration test coverage"
WEAK: "Helped with UI work"
STRONG: "Assisted in BTT UI/UX enhancements (US-2068094),
contributing to LaunchDarkly feature flag implementation"
Personal Reflection (One Flowing Paragraph)
- Write in first person, conversational, honest
- Cover: what you learned, what challenged you, what you want next
- Avoid: bullet points, headers, passive voice, corporate filler
Peer Feedback Templates
Strength:
[Name] consistently [specific behavior] which [impact].
For example, [concrete but general example].
Growth Area (constructive):
One area where [Name] could develop is [skill/behavior].
I believe strengthening this would [positive outcome].
Limited Collaboration Rule
- Keep it general: work ethic, communication style, team presence
- Do NOT mention specific story IDs
- Only state what you can directly verify
Asking for Feedback
Hi [Name], completing my performance review and would value your input.
Two questions if you have a moment:
1. One thing I did well you'd want me to keep doing
2. One area where I could improve
Even a few sentences helps. Thanks!
Pre-Submission Checklist
- Achievements are quantified where possible
- "Assisted in" used for non-primary contributions
- No filler phrases remain
- Personal reflection is prose, not bullets
- Required fields (EID, dates) are filled in
- Nothing is overstated
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 · 78 lines · 0 tokens per session scan A 293d91af038e
performance-review is a skill published in the GitHub repository jamestorrevillas/dev-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 545 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-08-31.
Other skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
go-dependency-audit
Go dependency audit specialist for CVE scanning (govulncheck), license risk triage, outdated dependency detection, upgrade impact analysis, and supply chain security. ALWAYS use when auditing go.mod dependencies, running govulncheck, checking license compatibility, planning dependency upgrades, or investigating supply…
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.
go-benchmark
Go performance benchmarking and pprof profiling specialist. ALWAYS use when writing benchmark functions (testing.B), generating or reading pprof profiles, interpreting flame graphs, finding memory allocation hotspots, comparing implementations with benchstat, or measuring ns/op / B/op / allocs/op. In Go code contexts…
pg-migration
PostgreSQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning PostgreSQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, constraint additions, RLS policy changes, or any DDL touching production tables. Covers lock-level analysis, CREATE INDEX…
create-pr
Create evidence-backed pull requests to the GitHub main branch with strict preflight, quality, and security gates. Use when users ask to create/submit/open/update a PR to main (including private repos), decide draft vs ready state, and provide reviewer-ready context for team review.