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 boshi-xixixi/TraeSkill --skill debian-linux-triagegit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/debian-linux-triage)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/debian-linux-triage"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/debian-linux-triage/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/boshi-xixixi/traeskill/debian-linux-triage"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/debian-linux-triage.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.00026 | $0.00220 |
| Opus 5 | $0.00013 | $0.00110 |
| Sonnet 5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
debian-linux-triage 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
Debian Linux Triage
You are a Debian Linux expert. Diagnose and resolve the user’s issue with Debian-appropriate tooling and practices.
Inputs
${input:DebianRelease}(optional)${input:ProblemSummary}${input:Constraints}(optional)
Instructions
- Confirm Debian release and environment assumptions; ask concise follow-ups if required.
- Provide a step-by-step triage plan using
systemctl,journalctl,apt, anddpkg. - Offer remediation steps with copy-paste-ready commands.
- Include verification commands after each major change.
- Note AppArmor or firewall considerations if relevant.
- Provide rollback or cleanup steps.
Output Format
- Summary
- Triage Steps (numbered)
- Remediation Commands (code blocks)
- Validation (code blocks)
- Rollback/Cleanup
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 · 32 lines · 26 tokens per session scan A 75ed743f3862
debian-linux-triage is a skill published in the GitHub repository boshi-xixixi/TraeSkill (263 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 220 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
debugging
A systematic method for finding the underlying cause of a software bug by observing the failure, forming a hypothesis, and testing it.
error-handling
A guide to handling failures and recording useful logs in software. It explains when to pass an error upward, recover, reduce functionality, or retry temporary failures.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
debugging
Systematic root-cause investigation for hard bugs.
azure-network-watcher
Expert knowledge for Azure Network Watcher development including troubleshooting, decision making, limits & quotas, security, configuration, and integrations & coding patterns. Use when configuring flow logs, Traffic Analytics, packet capture, VPN monitoring, or KQL/Terraform integrations, and other Azure Network…