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/gonzi-stack/deepseek-skills/deepseek-performancenpx skills add gonzi-stack/deepseek-skills --skill deepseek-performancegit clone --depth 1 https://github.com/gonzi-stack/deepseek-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/gonzi-stack/deepseek-skills/deepseek-performance)<a href="https://agentmods.dev/skills/gonzi-stack/deepseek-skills/deepseek-performance"><img src="https://agentmods.dev/badge/skills/gonzi-stack/deepseek-skills/deepseek-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.00114 | $0.03942 |
| Opus 5 | $0.00057 | $0.01971 |
| Sonnet 5 | $0.00023 | $0.00788 |
| Haiku 4.5 | $0.00011 | $0.00394 |
Grade A, and why
deepseek-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 — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepSeek Performance Skill — Universal
La optimización prematura es la raíz de todos los males. La optimización tardía es la raíz de los incidentes en producción. El camino correcto: medir → identificar el bottleneck real → optimizar ese bottleneck → medir de nuevo.
Principio fundamental
Nunca optimizar lo que no mediste. Cada optimización sin medición previa es una apuesta. A veces mejora algo irrelevante. Siempre tiene un costo: complejidad, mantenibilidad, legibilidad.
El ciclo correcto:
SÍNTOMA → MEDIR → BOTTLENECK REAL → HIPÓTESIS → OPTIMIZAR → MEDIR DE NUEVO
❌ El ciclo incorrecto:
SÍNTOMA → INTUICIÓN → OPTIMIZAR ALGO → ASUMIR QUE MEJORÓ
FASE 1 — Identificar el bottleneck real
1.1 Clasificar el síntoma antes de actuar
| Síntoma | Posibles causas | Dónde buscar primero |
|---|---|---|
| Request lento (>500ms) | N+1 queries, query sin índice, cómputo pesado, llamada externa | Logs de queries, tiempo de cada operación |
| Alto uso de CPU | Cómputo en el thread principal, loops costosos, serialización | Profiler de CPU |
| Alto uso de memoria | Leak de memoria, carga de datasets grandes, cache sin límite | Profiler de memoria, heap snapshots |
| Degradación bajo carga | Contención de recursos, pool de conexiones agotado, lock contention | Métricas de concurrencia |
| Lentitud progresiva | Memory leak, acumulación de datos, índices fragmentados | Tendencia en el tiempo |
1.2 Medir antes de tocar nada
// Para identificar dónde se va el tiempo en un request:
const t0 = performance.now();
const user = await userRepo.getById(id); // ¿cuánto tarda esto?
const t1 = performance.now();
const orders = await orderRepo.getByUser(id); // ¿y esto?
const t2 = performance.now();
const enriched = await enrichOrders(orders); // ¿y esto?
const t3 = performance.now();
console.log({
getUser: t1 - t0,
getOrders: t2 - t1,
enrich: t3 - t2,
total: t3 - t0,
});
// Solo después de ver estos números sabés qué optimizar
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 · 507 lines · 114 tokens per session scan A 54532c19d1ec
deepseek-performance is a skill published in the GitHub repository gonzi-stack/deepseek-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 114 tokens to every session and 3,942 once invoked, about $0.0006 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…