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 Quod-cmd/SystemLens --skill systemlens-troubleshootinggit clone --depth 1 https://github.com/Quod-cmd/SystemLensWrote 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/quod-cmd/systemlens/systemlens-troubleshooting)<a href="https://agentmods.dev/skills/quod-cmd/systemlens/systemlens-troubleshooting"><img src="https://agentmods.dev/badge/skills/quod-cmd/systemlens/systemlens-troubleshooting.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.00059 | $0.00326 |
| Opus 5 | $0.00030 | $0.00163 |
| Sonnet 5 | $0.00012 | $0.00065 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
systemlens-troubleshooting 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 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.
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
SystemLens Troubleshooting
Use the smallest relevant set of SystemLens tools. Start with a system overview only for broad or ambiguous symptoms; for a narrow report, call the targeted collector directly.
Treat unsupported, partial, access_denied, timeouts, and missing values as limitations. Never reinterpret them as healthy. Distinguish observed evidence from hypotheses and do not claim causation from correlation alone.
Before suggesting a user-performed troubleshooting change, create a temporary diagnostic snapshot containing only the categories needed to test the hypothesis. Explain the proposed change, its risk, and how to undo it. SystemLens itself is read-only and cannot authorize or perform the change.
After the user confirms they completed the change, compare the snapshot with current evidence. Report concrete deltas, note evidence that did not change, and say whether the hypothesis became more or less plausible. Delete the snapshot when the user asks, or allow it to expire automatically.
Prefer concise conversation text for diagnosis and next steps. Render the evidence card only when a baseline or before/after comparison is materially easier to understand visually.
Never request arbitrary commands, scripts, registry paths, file contents, browser history, keystrokes, screenshots, or raw Event Viewer dumps. Never reveal device credentials, OAuth tokens, or unsanitized profile paths.
What ships with it
1 file 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.
- 7d ago First seen · 19 lines · 59 tokens per session scan A f3c21a358bdb
systemlens-troubleshooting is a skill published in the GitHub repository Quod-cmd/SystemLens (0 stars, last pushed 11d ago), licensed MIT. It adds 59 tokens to every session and 326 once invoked, about $0.0003 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
seedance-troubleshoot
This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause diagnosis.
huawei-cloud-mrs-host-fault-diagnose
Huawei Cloud MRS cluster fault diagnosis skill. Diagnoses service faults, instance faults, and host faults through progressive root cause localization: quick log scan first, host troubleshooting when host issues are found, detailed investigation when no conclusion is reached. Driven by the built-in LakeWatch API…
huawei-cloud-mrs-host-alarm-diagnose
Huawei Cloud MRS cluster alarm diagnosis skill. Analyzes the root cause of an MRS alarm based on user-provided alarm information (alarm ID, alarm name, alarm details, occurrence time, node IP, related service and logs), then outputs the root cause, repair steps, and verification method. Diagnosis is driven by the…
mpm-doctor
Run diagnostic checks on Claude MPM installation.
debugging
Systematically diagnose and fix bugs using structured debugging techniques. Use when investigating errors, unexpected behavior, failing tests, or production issues.
seedance-troubleshoot
This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause diagnosis.