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 naiersaidane/claude-mastery --skill investiguegit clone --depth 1 https://github.com/naiersaidane/claude-masteryWrote 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/naiersaidane/claude-mastery/investigue)<a href="https://agentmods.dev/skills/naiersaidane/claude-mastery/investigue"><img src="https://agentmods.dev/badge/skills/naiersaidane/claude-mastery/investigue/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/naiersaidane/claude-mastery/investigue"><img src="https://agentmods.dev/badge/skills/naiersaidane/claude-mastery/investigue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00128 | $0.00626 |
| Opus 5 | $0.00064 | $0.00313 |
| Sonnet 5 | $0.00026 | $0.00125 |
| Haiku 4.5 | $0.00013 | $0.00063 |
Grade A, and why
investigue 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 12d 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.
What it actually says
Avant de commencer, vérifie que tu disposes de deux éléments :
- Le symptôme : ce qui se passe concrètement (message d'erreur, comportement observé, valeur retournée…)
- Le comportement attendu : ce qui devrait se passer à la place
Si l'un ou l'autre manque, demande-le explicitement avant d'aller plus loin.
Avant tout fix, déroule ces 4 phases dans l'ordre. Arrête-toi à la fin de chacune et attends ma validation.
PHASE 1 : Localiser et reproduire.
À partir du symptôme, explore le code (utilise le sous-agent Explore si nécessaire) pour identifier les 2-3 zones les plus susceptibles d'héberger la cause. Liste-les avec une phrase de justification chacune. Puis décris en 3 lignes le scénario minimal qui rejoue ce bug à coup sûr. Si tu ne peux pas le reproduire de manière fiable, dis-le et propose un plan pour y arriver.
PHASE 2 : 3 hypothèses classées sur la cause racine.
Propose 3 hypothèses sur la cause racine (pas le symptôme), classées de la plus probable à la moins probable. Pour chacune : hypothèse en 1 phrase, puis prédiction falsifiable — « si cette hypothèse est vraie, on observerait <observation précise> ; si on observe l'inverse, on l'élimine ».
PHASE 3 : Tester l'hypothèse #1.
Ajoute des logs ciblés pour vérifier l'hypothèse #1. Préfixe chaque log par le tag [DEBUG-a4f2] (4 caractères au hasard) pour suppression en bulk plus tard. Ne propose pas de fix à cette phase. Dis-moi ce que je dois observer pour confirmer ou infirmer.
Règle des 3 strikes : si les 3 hypothèses sont fausses, STOP. Ce n'est plus un bug de code, c'est une question d'architecture. On change d'angle.
PHASE 4 : Fix minimal.
Une fois l'hypothèse confirmée, propose les modifications les plus courtes qui traitent la cause racine. Pas d'optimisation collatérale, pas de refactor opportuniste. Rédige le message de commit en expliquant la cause racine, pas le symptôme.
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.
- 12d ago First seen · 29 lines · 128 tokens per session scan A 31b4be68913c
investigue is a skill published in the GitHub repository naiersaidane/claude-mastery (51 stars, last pushed 1mo ago), licensed MIT. It adds 128 tokens to every session and 626 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-30.
Other skills, from other repositories
spark-engineer
Use when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure…
debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting…
Reverse Engineering & Binary Analysis
Binary analysis, assembly interpretation, disassembly, decompilation, firmware RE, and protocol reverse engineering.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.