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/eaescob/resiliency_skills/performancenpx skills add eaescob/resiliency_skills --skill performancegit clone --depth 1 https://github.com/eaescob/resiliency_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/eaescob/resiliency_skills/performance)<a href="https://agentmods.dev/skills/eaescob/resiliency_skills/performance"><img src="https://agentmods.dev/badge/skills/eaescob/resiliency_skills/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 | $0.00084 | $0.01175 |
| Opus 5 | $0.00042 | $0.00588 |
| Sonnet 5 | $0.00017 | $0.00235 |
| Haiku 4.5 | $0.00008 | $0.00118 |
Grade A, and why
performance 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Testing
Implement load testing, benchmarking, and performance profiling.
Testing Types
| Type | Purpose | When to Use |
|---|---|---|
| Load Test | Validate expected traffic | Before launch, after changes |
| Stress Test | Find breaking point | Capacity planning |
| Soak Test | Find memory leaks | Before major releases |
| Benchmark | Compare implementations | During optimization |
Quick Start
Load Testing with k6
# Install k6
brew install k6 # macOS
# or: https://k6.io/docs/getting-started/installation/
# Run basic test
k6 run load-test.js
Basic load test script:
// load-test.js
import http from "k6/http"
import { check, sleep } from "k6"
export const options = {
stages: [
{ duration: "30s", target: 20 }, // Ramp up
{ duration: "1m", target: 20 }, // Stay at 20 users
{ duration: "10s", target: 0 }, // Ramp down
],
thresholds: {
http_req_duration: ["p(95)<500"], // 95% under 500ms
http_req_failed: ["rate<0.01"], // <1% errors
},
}
export default function () {
const res = http.get("http://localhost:3000/api/health")
check(res, {
"status is 200": (r) => r.status === 200,
"response time < 200ms": (r) => r.timings.duration < 200,
})
sleep(1)
}
Reference Guides
Load Testing
See references/load-testing.md for:
- k6 advanced configuration
- Testing authenticated endpoints
- CI/CD integration
Benchmarking
See references/benchmarking.md for:
- Node.js benchmarking
- Go benchmarking
- Database query benchmarking
Profiling
See references/profiling.md for:
- Node.js profiling (clinic.js, 0x)
- Go profiling (pprof)
- Memory leak detection
Performance Budgets
Set and enforce performance targets:
| Metric | Target | Critical |
|---|---|---|
| Time to First Byte (TTFB) | < 200ms | < 600ms |
| First Contentful Paint (FCP) | < 1.8s | < 3s |
| Largest Contentful Paint (LCP) | < 2.5s | < 4s |
| Cumulative Layout Shift (CLS) | < 0.1 | < 0.25 |
| API Response Time (p95) | < 500ms | < 1000ms |
| Error Rate | < 0.1% | < 1% |
What ships with it
3 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.
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 · 166 lines · 84 tokens per session scan A c13ad4d76d2d
performance is a skill published in the GitHub repository eaescob/resiliency_skills (2 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 84 tokens to every session and 1,175 once invoked, about $0.0004 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…