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/github/awesome-copilot/arch-linux-expertgit clone --depth 1 https://github.com/github/awesome-copilotWhat 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Arch Linux Expert — 100% identical, 0 lines differ
- Arch Linux Expert — 100% identical, 0 lines differ
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.
- 2d ago First seen · 55 lines · 23 tokens per session scan A 127c39f59c8c
Arch Linux Expert is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed today), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
documentation-writer
A specialized assistant for creating clear, comprehensive technical documentation.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
ndv-architect
Architecture advisor. Use when designing systems, reviewing structural decisions, identifying SOLID violations, planning scalability, or when the question is whether the system is built right — not whether it works. Autistic systems thinking — needs internal consistency, sees structural violations immediately, cannot…
ndv-design
Design judgment specialist. Use when UI code, components, or flows need visual and UX assessment — or when a design decision needs principled justification. Reads code as its rendered visual output. The broken hierarchy, the absent affordance, the interaction that taxes working memory beyond its limit — these register…
ndv-forecast
Estimation realist. Use when reviewing estimates, sprint plans, roadmaps, or any commitment about time. Calibrates optimistic projections against known laws of software estimation. Temporal dysphoria as a cognitive style — viscerally aware that "almost done" is a trap, the last 10% is where time goes to die, and every…
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.