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 agentmods add skills/drizzy07x/skillquiver/diagnose-systematicallynpx skills add Drizzy07x/Skillquiver --skill diagnose-systematicallygit clone --depth 1 https://github.com/Drizzy07x/SkillquiverWrote 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/drizzy07x/skillquiver/diagnose-systematically)<a href="https://agentmods.dev/skills/drizzy07x/skillquiver/diagnose-systematically"><img src="https://agentmods.dev/badge/skills/drizzy07x/skillquiver/diagnose-systematically.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 | $0.00031 | $0.00874 |
| Opus 5 | $0.00015 | $0.00437 |
| Sonnet 5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
diagnose-systematically 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose Systematically
Find the cause before proposing a fix. Diagnosis does not authorize implementation.
Preserve evidence
Keep an append-only investigation log with the symptom, commands, exit codes, decisive output, hypotheses, experiments, and verdicts. Put it in a scratch directory unless the user requested a versioned artifact. If the user requests read-only work or forbids edits, report that trail through command output and the final response; do not create any file, including a scratch or temporary log.
Evidence loop
- State the contract. Name the involved components, their expected behavior, and the exact observed symptom. Verify environment assumptions such as build, branch, configuration, and dependency versions.
- Make it fail. Run the smallest unattended signal that reaches the real symptom: focused test, CLI or HTTP assertion, headless UI check, trace replay, minimal harness, or seeded stress runner. A process starting, a string existing, or a silently skipped test is not a reproduction.
- Minimize. Remove one input, dependency, configuration value, or step at a time. Keep a removal only when the same symptom remains. For intermittent defects, measure a reproduction rate instead of treating one pass as proof.
- Form falsifiable hypotheses. First compare a working example of the same pattern with the failing path. Write only credible hypotheses, each with a distinguishing prediction and falsifier.
- Probe one variable. Observe state at the earliest boundary where the predictions diverge. Revert probes or instrumentation that did not explain the symptom before trying the next one.
- Claim only what discriminates. A cause is verified only when its prediction is observed through the symptom-specific signal and plausible alternatives are ruled out. Separate verified cause, inference, and proposed behavior change in the report.
A useful signal is symptom-specific, red-capable, deterministic or measured, fast enough to repeat, and agent-runnable. If no such signal can be built, report the attempts and request the smallest missing artifact or access.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 83 lines · 31 tokens per session scan A 1206b35f6360
diagnose-systematically is a skill published in the GitHub repository Drizzy07x/Skillquiver (2 stars, last pushed 12d ago), licensed MIT. It adds 31 tokens to every session and 874 once invoked, about $0.0002 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 skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…