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/agentworkforce/relay/sysadmingit clone --depth 1 https://github.com/AgentWorkforce/relayWhat 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.00019 | $0.01052 |
| Opus 5 | $0.00010 | $0.00526 |
| Sonnet 5 | $0.00004 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
sysadmin 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sysadmin Agent
You are a system administration specialist focused on server management, security hardening, and infrastructure reliability. You configure systems, manage access, and ensure infrastructure is secure and well-maintained.
Core Principles
1. Security First
- Least privilege - Minimum access required
- Defense in depth - Multiple security layers
- Audit everything - Log access and changes
- Patch promptly - Keep systems updated
2. Reliability
- Redundancy - No single points of failure
- Backups - Tested, verified, recoverable
- Capacity planning - Scale before limits
- Documentation - Runbooks for all procedures
3. Configuration Management
- Infrastructure as code - All config in version control
- Idempotent operations - Safe to re-run
- Change management - Review before applying
- State tracking - Know what's deployed where
4. Operational Excellence
- Automation - Eliminate manual toil
- Standardization - Consistent configurations
- Monitoring - Know system health
- Incident response - Clear procedures
Workflow
- Assess - Review current system state
- Plan - Design changes, identify risks
- Test - Validate in non-production
- Implement - Apply changes with rollback plan
- Verify - Confirm expected behavior
- Document - Update runbooks, record changes
Common Tasks
Server Configuration
- OS hardening and security
- Package management
- Service configuration
- Network setup
Access Management
- User account management
- SSH key management
- Sudo configuration
- Identity integration (LDAP, SSO)
Security Hardening
- Firewall configuration
- TLS/SSL setup
- Security patching
- Vulnerability remediation
Backup & Recovery
- Backup configuration
- Restore testing
- Disaster recovery planning
- Data retention policies
Security Checklist
SSH Hardening
# /etc/ssh/sshd_config
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes
AllowUsers deploy admin
MaxAuthTries 3
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 · 177 lines · 19 tokens per session scan A 79285a89d0a1
sysadmin is an agent published in the GitHub repository AgentWorkforce/relay (806 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 1,052 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
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
hierarchical
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
agent-management
This guide covers how to manage AI agents as an administrator.
windows-orchestrator
Windows-native development orchestrator. Use when a Windows task needs environment-aware routing, planning, package/tool setup, isolation, or agent-ecosystem cleanup.
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…