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/kid-sid/codex-spellbook/performancenpx skills add kid-sid/codex-spellbook --skill performancegit clone --depth 1 https://github.com/kid-sid/codex-spellbookWhat 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.00037 | $0.03845 |
| Opus 5 | $0.00018 | $0.01922 |
| Sonnet 5 | $0.00007 | $0.00769 |
| Haiku 4.5 | $0.00004 | $0.00384 |
Grade A, and why
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 2d 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.
tasks = [fetch(session, url) for url in urls] How it starts
The opening of the file, as written. The whole thing — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance
A structured guide to profiling, caching, database optimization, async patterns, and performance budgets for production services.
When to Activate
- Profiling a slow endpoint or service
- Implementing a caching layer (in-process, Redis, or HTTP)
- Optimizing a database query or fixing N+1 problems
- Setting a performance budget for an API endpoint
- Reducing memory usage or GC pressure
- Choosing between sync and async patterns for a workload
Profiling
When to Profile
- Profile before optimizing — never guess where the bottleneck is
- CPU profiling — where is time spent (function call time)?
- Memory profiling — what objects are consuming heap space?
- I/O profiling — what is blocking on disk or network?
Python — cProfile + snakeviz
import cProfile
import pstats
import io
pr = cProfile.Profile()
pr.enable()
result = my_slow_function()
pr.disable()
s = io.StringIO()
ps = pstats.Stats(pr, stream=s).sort_stats('cumulative')
ps.print_stats(20) # top 20 slowest functions
print(s.getvalue())
# Profile a whole script from the command line:
# python -m cProfile -o output.prof script.py
# snakeviz output.prof # opens interactive flame graph in browser
Memory profiling with memory_profiler:
# pip install memory-profiler
from memory_profiler import profile
@profile
def my_function():
# annotated line-by-line memory usage
data = [x for x in range(10_000_000)]
return data
TypeScript/Node.js — clinic.js + 0x
# CPU flame graph
npx 0x -- node dist/server.js
# Opens a generated .html flame graph in the browser
# Heap snapshot + event loop lag
npx clinic doctor -- node dist/server.js
# CPU flame graph via clinic
npx clinic flame -- node dist/server.js
# Async waterfall / I/O bottlenecks
npx clinic bubbleprof -- node dist/server.js
Go — pprof
import (
"net/http"
_ "net/http/pprof" // side-effect import registers /debug/pprof handlers
)
// In main(), run alongside your app server:
go func() {
http.ListenAndServe("localhost:6060", nil)
}()
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.
- 2d ago First seen · 486 lines · 37 tokens per session scan A 79bc2170d2de
performance is a skill published in the GitHub repository kid-sid/codex-spellbook (21 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 3,845 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.