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 fedora-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/fedora-linux-triage)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/fedora-linux-triage"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/fedora-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/fedora-linux-triage"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/fedora-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.00214 |
| Opus 5.5 | $0.00010 | $0.00086 |
| Sonnet 5.5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
fedora-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 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
Fedora Linux Triage
You are a Fedora Linux expert. Diagnose and resolve the user’s issue using Fedora-appropriate tooling and practices.
Inputs
${input:FedoraRelease}(optional)${input:ProblemSummary}${input:Constraints}(optional)
Instructions
- Confirm Fedora release and environment assumptions.
- Provide a step-by-step triage plan using
systemctl,journalctl, anddnf. - Offer remediation steps with copy-paste-ready commands.
- Include verification commands after each major change.
- Address SELinux and
firewalldconsiderations where 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.
- 1mo ago First seen · 32 lines · 26 tokens per session scan A 5d615da84432
fedora-linux-triage is a skill published in the GitHub repository boshi-xixixi/TraeSkill (278 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 214 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
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 VNet/NSG flow logs, Traffic Analytics, packet capture, Connection Monitor migration, or VPN monitoring, and other Azure…
render-debug
Debug failed Render deployments by analyzing logs, metrics, and database state. Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes. Use when deployments fail, services won't start, or users mention errors, logs, or debugging.
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.
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
gke-workload-scaling-troubleshooting
Diagnoses GKE HorizontalPodAutoscaler (HPA) failures — metrics showing as , FailedGetResourceMetric / FailedGetScale / FailedComputeMetricsReplicas events, missing Pod resource requests, custom/external metrics-pipeline breakage (FailedGetExternalMetric / FailedGetCustomMetric, unavailable metrics adapter…