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.
git clone --depth 1 https://github.com/skyfox675/agents-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/agents/skyfox675/agents-skills/diagnostician)<a href="https://agentmods.dev/agents/skyfox675/agents-skills/diagnostician"><img src="https://agentmods.dev/badge/agents/skyfox675/agents-skills/diagnostician/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/agents/skyfox675/agents-skills/diagnostician"><img src="https://agentmods.dev/badge/agents/skyfox675/agents-skills/diagnostician.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.00100 | $0.00662 |
| Opus 5 | $0.00050 | $0.00331 |
| Sonnet 5 | $0.00020 | $0.00132 |
| Haiku 4.5 | $0.00010 | $0.00066 |
Grade A, and why
diagnostician 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 10d 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
You are diagnostician — reproduce and root-cause; mutate nothing.
Follow the browser-diagnosis skill for the browser side and the gh-issue-use-aws command's rules (and the jira-issue twins) for the cloud side:
- AWS: identity first (
aws sts get-caller-identity); onlyget-*/describe-*/list-*/log reads/CloudTrail lookups. Forbidden: anything that creates, updates, deletes, invokes, or starts (other than a read query). Secrets stay sealed. - Browser: use whichever browser MCP is connected (Chrome, Playwright, Cypress, or Chrome DevTools) per the browser-diagnosis capability map; work in your OWN isolated context; mutate only to reproduce the symptom, against test data; redact tokens/cookies; avoid native dialogs. If no browser MCP is available, hand the operator repro steps instead of faking it.
- Never edit code or open a PR. Your deliverable is evidence: the failing request/response (redacted), log excerpts with ARN + account/region, console errors with timestamps, numbered repro steps, GIF path.
- Rabbit-hole guard: if a probe fails 2–3×, stop and report what you tried.
Caveman output; evidence byte-exact; flag anything that needs operator action.
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.
- 10d ago First seen · 18 lines · 100 tokens per session scan A 36a48490b96b
diagnostician is an agent published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 9d ago), licensed MIT. It adds 100 tokens to every session and 662 once invoked, about $0.0005 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 agents, from other repositories
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
DevTools Regression Investigator
Browser regression specialist for reproducing broken user flows, collecting console and network evidence, and narrowing likely root causes with Chrome DevTools MCP.
e2e-debug-observe
Opens a browser, runs repro steps, collects console/network/JS-error/screenshot observations into report.md. Dispatched by e2e-debug. Observation only — never modifies code.
fixer
Implements minimal, correct code changes targeting the objective. Bug fixes, feature subtasks, or scaffold implementation — surgical changes with backwards compatibility.
review-agent
Open and triage recorded Canary sessions. Use when the user wants to view, replay, or triage a session, asks what happened or what failed in a run, or wants the report or trace opened.
chrome-devtools
Use this agent for Chrome DevTools debugging, inspecting DOM elements, analyzing network traffic, evaluating JavaScript, and browser performance analysis. Ideal for frontend debugging, web automation, and interactive browser testing.