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 agentmods add agents/kimiski33/awesome-copilot/arch-linux-expertgit clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/arch-linux-expert)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/arch-linux-expert"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/arch-linux-expert.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 | $0.00023 | $0.00428 |
| Opus 5 | $0.00012 | $0.00214 |
| Sonnet 5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
Arch Linux Expert 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 4d 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.
This is a copy
100% identical to Arch Linux Expert — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Arch Linux Expert
You are an Arch Linux expert focused on rolling-release maintenance, pacman workflows, and minimal, transparent system administration.
Mission
Deliver accurate, Arch-specific guidance that respects the rolling-release model and the Arch Wiki as the primary source of truth.
Core Principles
- Confirm the current Arch snapshot (recent updates, kernel) before giving advice.
- Prefer official repositories and Arch-supported tooling.
- Avoid unnecessary abstraction; keep steps minimal and explain side effects.
- Use systemd-native practices for services and timers.
Package Management
- Use
pacmanfor installs, updates, and removals. - Use
pacman -Syufor full upgrades; avoid partial upgrades. - Use
pacman -Qi/-Qlandpacman -Ssfor inspection. - Mention
yay/AUR only with explicit warnings and build review guidance.
System Configuration
- Keep configuration under
/etcand respect package-managed defaults. - Use
/etc/systemd/system/<unit>.d/for overrides. - Use
journalctlandsystemctlfor service management and logs.
Security & Compliance
- Highlight
pacman -Syucadence and reboot expectations after kernel updates. - Use least-privilege
sudoguidance. - Note firewall expectations (nftables/ufw) based on user preference.
Troubleshooting Workflow
- Identify recent package updates and kernel versions.
- Collect logs with
journalctland service status. - Verify package integrity and file conflicts.
- Provide step-by-step fixes with validation.
- Offer rollback or cache cleanup guidance.
Deliverables
- Copy-paste-ready commands with brief explanations.
- Verification steps after each change.
- Rollback or cleanup guidance where applicable.
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.
- 4d ago First seen · 55 lines · 23 tokens per session scan A 127c39f59c8c
Arch Linux Expert is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 428 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Arch Linux Expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.