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 FlorianBruniaux/claude-code-plugins --skill diagnosegit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/diagnose)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/diagnose"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/diagnose/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/florianbruniaux/claude-code-plugins/diagnose"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/diagnose.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.00010 | $0.01331 |
| Opus 5.5 | $0.00004 | $0.00532 |
| Sonnet 5.5 | $0.00002 | $0.00266 |
| Haiku 4.5 | $0.00001 | $0.00133 |
Grade D, and why
diagnose scanned grade D with 3 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 1mo 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -sL "https://raw.githubusercontent.com/flobby41/claude-code-ultimate-guide/main/examples/scripts/audit-scan.sh" | bash -s -- --json 2>/dev/null Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/settings.json 2>/dev/null || echo "No global settings" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL "https://raw.githubusercontent.com/flobby41/claude-code-ultimate-guide/main/guide/ultimate-guide.md" | head -n 3000 How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Diagnostic Assistant
Interactive troubleshooting assistant for Claude Code issues. Supports FR/EN.
Instructions
You are an expert diagnostic assistant for Claude Code problems. Your role is to identify issues and provide targeted solutions.
Step 1: Language Detection
Detect the user's language from their input. If ambiguous, ask:
"FR or EN? / Français ou English?"
Respond in the detected language throughout the session.
Step 2: Fetch Knowledge Base
Silently fetch the troubleshooting reference:
# Fetch the latest troubleshooting guide from the repo
curl -sL "https://raw.githubusercontent.com/flobby41/claude-code-ultimate-guide/main/guide/ultimate-guide.md" | head -n 3000
Use Section 10.4 (Troubleshooting) as your primary reference.
Step 3: Environment Scan
Run the audit scanner to understand the user's setup:
# Run audit-scan.sh in JSON mode for structured data
curl -sL "https://raw.githubusercontent.com/flobby41/claude-code-ultimate-guide/main/examples/scripts/audit-scan.sh" | bash -s -- --json 2>/dev/null
If the script fails, fall back to manual checks:
# Global config
cat ~/.claude/settings.json 2>/dev/null || echo "No global settings"
# Project config
cat .claude/settings.json 2>/dev/null || echo "No project settings"
# CLAUDE.md files
ls -la CLAUDE.md .claude/CLAUDE.md ~/.claude/CLAUDE.md 2>/dev/null
# MCP config
cat ~/.claude.json 2>/dev/null | jq '.mcpServers // empty' || echo "No MCP config"
Step 4: Present Categories
If the user hasn't described a specific problem, present these categories:
Permissions
- Repeated permission prompts despite settings.json / Demandes répétées malgré settings.json
- Actions blocked by hooks / Actions bloquées par hooks
MCP Servers 3. Server not found / connection failed / Serveur non trouvé 4. MCP tool not recognized / Outil MCP non reconnu
Configuration 5. settings.json ignored / settings.json ignoré 6. CLAUDE.md not read / CLAUDE.md non lu 7. Hooks not triggering / Hooks ne se déclenchent pas
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.
- 1mo ago First seen · 216 lines · 10 tokens per session scan D a5281a82f19e
diagnose is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (42 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 1,331 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it D with 3 findings (downloads and executes remote code, reads agent configuration directories, 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
pentest-forensics
Digital forensics — evidence acquisition, memory/disk imaging analysis, timeline reconstruction, IOC extraction advisory. Triggers on forensics, DFIR, Volatility, memory analysis, disk image, Autopsy, FTK, timeline, IOC extraction, evidence chain, log analysis.
pentest-malware
Malware analysis — triage, static analysis, dynamic sandbox, IOC extract, YARA signature writing advisory. Triggers on malware analiz, malware triage, sandbox, Cuckoo, IDA, Ghidra, dynamic analysis, IOC, YARA imza, packer, unpacker, reverse malware.
security-check
Comprehensive AI-powered security scanning suite with 48 skills covering OWASP Top 10, 7 language-specific deep scanners (Go, TypeScript, Python, PHP, Rust, Java, C#), supply chain analysis, infrastructure-as-code scanning, and 3000+ checklist items. Use when you need to run a security audit, find vulnerabilities…
expo-troubleshooting
Common Expo errors: Metro cache, version mismatch, expo-doctor, Pod install, Gradle daemon, native module conflicts, EAS Build logs, dependency hoisting. Triggers on expo error, metro cache, version mismatch, expo-doctor, expo install check, pod install error, gradle error, native module not found, build failed, eas…
skill-repair
Diagnose and fix failing or degraded skills automatically - systemic-first triage, per-category playbooks, and a verification plan.
self-improve
Improve the agent itself, or audit its recent performance - better skills, prompts, workflows, and config, plus a quality/reliability/memory-hygiene review of what it did and what failed.