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 atretyak1985/swarmery --skill troubleshootinggit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/troubleshooting)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/troubleshooting"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/troubleshooting/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/atretyak1985/swarmery/troubleshooting"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/troubleshooting.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.00043 | $0.00849 |
| Opus 5 | $0.00022 | $0.00425 |
| Sonnet 5 | $0.00009 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
troubleshooting 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 9d 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.
Known issues are grepped for "telemetry", matching "Telemetry Not Appearing" → main-app logs read → SSE stream probed with curl → upstream WebSocket found refused → main app restarted → telemetry confirmed flowing. You g How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Diagnose and resolve operational issues on the project's platform (project.json → domainTerms.product): device connectivity, telemetry streaming, migrations, image pulls, performance, CI/CD deploy-path failures. Structured incident response: known-issue search, triage with severity (P0-P3), evidence-based diagnosis, recovery, postmortem. Reactive debugging only.
Rules (never violate)
- Write is scoped to postmortems and diagnostic reports only — never modify source code, deployment values, or manifests during an incident.
- Before any destructive recovery (rollback, rollout undo, scale-to-zero, schema-history edits): snapshot via
/<envAlias>-health, then confirm with the operator. - Grep
resources/common-issues.mdfor symptom keywords before fresh diagnosis; read only the matching section. - Mark inferred (not log-evidenced) root causes
[SUSPECTED]. - Every P0/P1 incident gets a postmortem in the incident docs directory, never in source trees.
- Use the environment variables (
INGRESS_DOMAIN,REGISTRY_HOST, …), never hardcoded environment strings.
Resources
- Read
resources/diagnostic-procedures.mdwhen working an incident: the 5-step procedure, diagnostic patterns, environment variables, severity table, postmortem template, self-check, escalation, the CI/CD failure taxonomy (P-017…P-026), and failure modes. - Grep
resources/common-issues.mdwhen matching a symptom — 12+ known patterns with verified solutions; never load the whole file. - Run
scripts/diagnose.sh [namespace]for a cluster snapshot — pods, events, ingress, health, resources.
How to use
What it does
Walks you through a live operational failure — a device that stopped connecting, missing telemetry, a pod stuck pulling an image, a failed deploy job. It searches a bundled known-issues catalogue first, assigns a severity, gathers evidence from logs and cluster state, and proposes recovery commands — operational commands only, never source edits.
When to use it
What ships with it
3 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.
- 9d ago First seen · 64 lines · 43 tokens per session scan A c98a8ecb7f72
troubleshooting is a skill published in the GitHub repository atretyak1985/swarmery (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 43 tokens to every session and 849 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
debugging
This skill should be used when a test is failing inexplicably, when a runtime error appears in production, when a bug reproduces unpredictably, or when two or more prior fix attempts have failed. Provides a 4-phase systematic debugging workflow — investigate, analyze patterns, form hypothesis, fix with test — to…
gh-actions-failure-triage
Inspect failing GitHub Actions checks, isolate the actionable failure, and turn it into a concrete fix path with verification steps.
ci-fix
Use when "CI is red", "fix the checks", or "make CI green", one check needs classifying, or a bounded sweep runs. Not for deploys, credentials, or rerun-as-fix. Non-CI bugs: use strike-the-root.
classify-ci-failure
Use when a CI check is failed, absent, pending too long, unstable, or reported unexpectedly. Classify it into a deterministic failure class with the next owner, then emit a reviewable fix plan, without patching. Not for sweeping and patching — use ci-sweeper.
ci-sweeper
Use when a requested sweep monitors CI failures over a bounded attempt window. Returns each root cause reproduced or classified non-actionable with any minimal verified patch as a proposal. Not for classifying one failure without patching — use classify-ci-failure.