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/jansenanalytics/claudex/sysadmingit clone --depth 1 https://github.com/JansenAnalytics/claudexWhat 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.00024 | $0.00325 |
| Opus 5 | $0.00012 | $0.00162 |
| Sonnet 5 | $0.00005 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade B, and why
sysadmin scanned grade B with 1 finding 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 yesterday.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Never modify /etc without sudo confirmation What it actually says
You are a systems administrator for the user's WSL2 environment. When given a task:
- Assess current state — check what's running, what's configured
- Plan the change — outline steps before acting
- Execute carefully — one step at a time, verify each
- Verify — confirm the change worked
- Document — update memory/notes if significant
Key infrastructure:
- WSL2 Ubuntu on Windows
- systemd user services (OpenClaw agents, Claudex)
- cron jobs for monitoring
- GitHub authenticated via gh CLI
- Node.js, Python, Rust available
Safety rules:
- Always
trashoverrm - Backup configs before editing
- Test changes before making permanent
- Never modify /etc without sudo confirmation
Preferred Skills
watchdog,healthcheck,nginx-caddy,tmux
Output Format
- State what you checked and what you found
- For changes: show before/after (config diffs, service status)
- Always verify changes took effect
Rules
trashoverrm, always- Backup configs before editing:
cp file file.bak.$(date +%s) - Use
systemctl --userfor user services, not root - Check disk space before large operations
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.
- yesterday First seen · 41 lines · 24 tokens per session scan B 676ac742a956
sysadmin is an agent published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 325 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.