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 ntaffzii/Skill-Agents --skill diagnosegit clone --depth 1 https://github.com/ntaffzii/Skill-AgentsWrote 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/ntaffzii/skill-agents/diagnose)<a href="https://agentmods.dev/skills/ntaffzii/skill-agents/diagnose"><img src="https://agentmods.dev/badge/skills/ntaffzii/skill-agents/diagnose.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.1 | $0.00055 | $0.00549 |
| Opus 5 | $0.00028 | $0.00275 |
| Sonnet 5 | $0.00011 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
diagnose 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 7d 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.
- Prefer a fast deterministic signal: failing test, CLI command, curl script, browser script, replay harness, or benchmark. How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose
Use this skill to find root cause before changing code.
Core Rule
Build a reliable feedback loop before committing to a hypothesis. If there is no runnable signal, create one or explain exactly what is missing.
Mantra
Reproduce, trace, falsify, validate.
Workflow
-
Reproduce
- Capture exact steps, inputs, environment, command, request, fixture, or UI path.
- Prefer a fast deterministic signal: failing test, CLI command, curl script, browser script, replay harness, or benchmark.
- If flaky, raise the reproduction rate with loops, stress, narrowed timing, pinned seeds, or isolated state.
-
Minimize
- Reduce the repro to the smallest case that still shows the bug.
- Confirm the minimized failure is the same symptom the user reported.
- Avoid fixing a nearby but different failure.
-
Generate hypotheses
- List 3 to 5 ranked hypotheses before testing.
- For each, state a falsifiable prediction.
- Prefer the hypothesis that explains every observed breadcrumb, not only the latest one.
-
Instrument
- Test one variable at a time.
- Prefer debugger or REPL inspection when available.
- Use targeted logs only at boundaries that distinguish hypotheses.
- Tag temporary logs with a unique prefix such as
[DEBUG-a4f2]. - Keep a short ledger of experiments and observations when the investigation has more than one branch.
-
Fix
- Write or preserve a regression signal before the fix when a correct seam exists.
- Apply the smallest change that addresses the root cause.
- Re-run the original repro and the minimized repro.
-
Clean up
- Remove temporary instrumentation.
- Delete throwaway harnesses or move them to a clearly named debug location.
- State the root cause, mechanism, fix, and verification.
Stop Conditions
Stop and ask for missing artifacts when:
- The issue cannot be reproduced locally.
- The only repro depends on an external system the agent cannot access.
- The user has logs, HAR files, screenshots, traces, or environment details that are required.
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.
- 7d ago First seen · 71 lines · 55 tokens per session scan A 845c4edb42f6
diagnose is a skill published in the GitHub repository ntaffzii/Skill-Agents (4 stars, last pushed 5d ago), licensed MIT. It adds 55 tokens to every session and 549 once invoked, about $0.0003 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-31.
Other skills, from other repositories
social-physics-filter
Unified boundary enforcement, interpersonal diagnostic, and relational audit engine. Absorbs 40 psychology + 2 social protocols and all relationship case studies.
therapeutic-ifs
Unified inner work engine: Schema deconstruction (diagnosis) + IFS therapy (treatment). Absorbs: schema-deconstruction.
Diagnostic-First Refactoring
A non-destructive, decoupled analysis protocol for refactoring code. Generates a "Bill of Materials" report before any code is touched.
diagnostic-first-refactoring
Analyze codebase structure before making changes — the "Surgeon's Scan" pattern.
operate-a2a-superhub
Operate and diagnose the A2A Superhub product across its CLI, HTTP, and declared MCP/A2A surfaces. Use when the user explicitly asks to inspect a Superhub, create or read Superhub tasks or artifacts, work with Superhub memory/inbox/wakeup/handoffs, validate this product skill, diagnose auth/index/queue/capability…
sentry
Sentry error tracking and performance monitoring. Use for error tracking.