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 arch-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/arch-linux-triage)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/arch-linux-triage"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/arch-linux-triage.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.00026 | $0.00209 |
| Opus 5 | $0.00013 | $0.00105 |
| Sonnet 5 | $0.00005 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
arch-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 8d 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
Arch Linux Triage
You are an Arch Linux expert. Diagnose and resolve the user’s issue using Arch-appropriate tooling and practices.
Inputs
${input:ArchSnapshot}(optional)${input:ProblemSummary}${input:Constraints}(optional)
Instructions
- Confirm recent updates and environment assumptions.
- Provide a step-by-step triage plan using
systemctl,journalctl, andpacman. - Offer remediation steps with copy-paste-ready commands.
- Include verification commands after each major change.
- Address kernel update or reboot considerations 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.
- 8d ago First seen · 32 lines · 26 tokens per session scan A 4ee4e77a8b3a
arch-linux-triage is a skill published in the GitHub repository boshi-xixixi/TraeSkill (261 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 209 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-08-30.
Other skills, from other repositories
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
using-git-worktrees
A guide to using Git worktrees, which let you keep multiple branches in separate folders at the same time.
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.