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 beel-collab/presets.dev --skill claude-monitorgit clone --depth 1 https://github.com/beel-collab/presets.devWrote 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/beel-collab/presets.dev/claude-monitor)<a href="https://agentmods.dev/skills/beel-collab/presets.dev/claude-monitor"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/claude-monitor/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/beel-collab/presets.dev/claude-monitor"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/claude-monitor.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.00037 | $0.01591 |
| Opus 5 | $0.00018 | $0.00796 |
| Sonnet 5 | $0.00007 | $0.00318 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
claude-monitor 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 11d 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.
This is a copy
92% identical to claude-monitor — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Monitor — Diagnóstico de Performance
Overview
Monitor de performance do Claude Code e sistema local. Diagnostica lentidao, mede CPU/RAM/disco, verifica API latency e gera relatorios de saude do sistema.
When to Use This Skill
- When the user mentions "lento" or related topics
- When the user mentions "lentidao" or related topics
- When the user mentions "lag" or related topics
- When the user mentions "lagado" or related topics
- When the user mentions "travando" or related topics
- When the user mentions "claude lento" or related topics
Do Not Use This Skill When
- The task is unrelated to claude monitor
- A simpler, more specific tool can handle the request
- The user needs general-purpose assistance without domain expertise
How It Works
Skill para diagnosticar e resolver problemas de lentidão no Claude Code e no sistema. Determina se o gargalo é local (PC) ou remoto (API Claude) e sugere ações corretivas.
Quando Usar
- Usuário reclama que o Claude Code está lento ou travando
- Troca de sessões de conversa demora para carregar
- Respostas do Claude demoram muito
- PC parece lento enquanto usa o Claude Code
- Qualquer menção a performance, lag, lentidão
1. Diagnóstico Rápido (Health_Check.Py)
Rode SEMPRE como primeiro passo:
python C:\Users\renat\skills\claude-monitor\scripts\health_check.py
O script analisa em ~3 segundos:
- CPU: Uso atual e por core. >80% = gargalo provável
- RAM: Total, usada, disponível. >85% = pressão de memória
- Browsers: Processos e RAM por browser. >5GB total = excesso de abas
- Claude Code: Processos e RAM consumida
- Disco: Espaço livre. <10% = impacto em swap/performance
- Rede: Latência ao endpoint da API Claude
- Diagnóstico: Classificação automática do problema com sugestões
2. Interpretar O Resultado
O script retorna um JSON com diagnosis contendo:
bottleneck: "cpu" | "ram" | "browsers" | "disk" | "network" | "claude_api" | "ok"severity: "critical" | "warning" | "ok"suggestions: Lista de ações recomendadassummary: Resumo em português para mostrar ao usuário
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.
- 11d ago First seen · 173 lines · 37 tokens per session scan A e85df0aff067
claude-monitor is a skill published in the GitHub repository beel-collab/presets.dev (3 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 1,591 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to claude-monitor, differing in 23 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Applies a modified Fagan Inspection methodology to resolve persistent bugs and complex issues. Use when several fix or debugging attempts have already failed and a methodical root-cause analysis warranting a Fagan inspection is needed. For first-pass diagnosis of a reproducible bug or regression use…
reframe-voice
Write, rewrite, or review content in the evidence-led reframe voice style. Use when the user explicitly asks to write in "reframe voice" or "reframe style". Do NOT use for general writing tasks.
qa-to-issues
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Use when user wants to report bugs in their own codebase and create Github issues conversationally.
diagnose-hard-problem
Disciplined diagnosis loop for hard problems, diagnosing bugs and regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test.
agents-sdk-typescript-debugging
Use when troubleshooting an agent built with the Microsoft Agents SDK (@microsoft/agents-hosting and related packages). Trigger on any of these symptoms: build or TypeScript errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, .env configuration problems, Azure AD…
agents-sdk-dotnet-debugging
Use when troubleshooting an agent built with the Microsoft Agents SDK (Microsoft.Agents.Hosting.AspNetCore and related packages) in C# / .NET. Trigger on any of these symptoms: build or C# compile errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, appsettings.json…