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 strands-agents/samples --skill technical-troubleshootinggit clone --depth 1 https://github.com/strands-agents/samplesWrote 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/strands-agents/samples/technical-troubleshooting)<a href="https://agentmods.dev/skills/strands-agents/samples/technical-troubleshooting"><img src="https://agentmods.dev/badge/skills/strands-agents/samples/technical-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/strands-agents/samples/technical-troubleshooting"><img src="https://agentmods.dev/badge/skills/strands-agents/samples/technical-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00178 |
| Opus 5.5 | $0.00015 | $0.00071 |
| Sonnet 5.5 | $0.00008 | $0.00036 |
| Haiku 4.5 | $0.00004 | $0.00018 |
Grade A, and why
technical-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 1mo 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
Technical Troubleshooting Skill
You are the specialist for setup and troubleshooting requests.
When this skill is activated:
- Call
get_technical_supportwith the user's issue to retrieve step-by-step guidance. - Use
file_readto reviewskills/technical-troubleshooting/references/escalation-guide.mdif the issue sounds safety-related, hardware-failure-related, or unresolved after the first troubleshooting pass. - Provide a clear, step-by-step answer when possible.
- If the issue remains unresolved, recommend the appropriate escalation path.
Do not skip the knowledge-base lookup for technical questions.
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.
- 1mo ago First seen · 19 lines · 38 tokens per session scan A ab3b9b87d5f5
technical-troubleshooting is a skill published in the GitHub repository strands-agents/samples (909 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 178 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
ai-equipment-failure-rca-draft
A root-cause analysis draft assistant for investigating equipment failures. Root-cause analysis means looking for the underlying reason a failure happened, not only its visible symptom.
spark-environment-setup
Set up a working ML training/inference environment on NVIDIA DGX Spark (GB10, aarch64, CUDA 13). Use when installing PyTorch/Unsloth/TRL/vLLM on DGX Spark, hitting libcudart or wheel-ABI errors on aarch64, or choosing between NGC containers and bare pip installs.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.
terraform-module-library
Build reusable Terraform modules for AWS, Azure, GCP, and OCI infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.
raspberry-pi-pico2
Use when developing with Raspberry Pi Pico 2 or the Pi Debug Probe.