Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JansenAnalytics/claudexnpx agentmods add skills/jansenanalytics/claudex/systemd-managerWrote 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/jansenanalytics/claudex/systemd-manager)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/systemd-manager"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/systemd-manager.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.00044 | $0.01301 |
| Opus 5 | $0.00022 | $0.00651 |
| Sonnet 5 | $0.00009 | $0.00260 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade B, and why
systemd-manager 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systemctl start myapp How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systemd Manager Skill
Create and manage systemd services, timers, and socket units.
Use When
- Creating background services or daemons
- Setting up scheduled timers (modern cron alternative)
- Debugging failed units or viewing logs
- Managing service dependencies and ordering
Quick Reference
Service Management
# Start / stop / restart
sudo systemctl start myapp
sudo systemctl stop myapp
sudo systemctl restart myapp
sudo systemctl reload myapp # reload config without restart
# Enable at boot / disable
sudo systemctl enable myapp
sudo systemctl enable --now myapp # enable + start
# Status
systemctl status myapp
systemctl is-active myapp
systemctl is-enabled myapp
# List all services
systemctl list-units --type=service
systemctl list-units --type=service --state=failed
# Show unit file
systemctl cat myapp
# Reload after editing unit files
sudo systemctl daemon-reload
Journalctl (Logs)
# Logs for a service
journalctl -u myapp
# Follow (tail -f equivalent)
journalctl -u myapp -f
# Last 100 lines
journalctl -u myapp -n 100
# Since time
journalctl -u myapp --since "1 hour ago"
journalctl -u myapp --since "2024-01-15 09:00"
# Only errors
journalctl -u myapp -p err
# Disk usage / vacuum
journalctl --disk-usage
sudo journalctl --vacuum-size=500M
# Boot logs
journalctl -b # current boot
journalctl -b -1 # previous boot
# Kernel messages
journalctl -k
Timers (Cron Replacement)
# List active timers
systemctl list-timers --all
# Timer unit example — runs every 15 minutes
# /etc/systemd/system/backup.timer
# [Timer]
# OnCalendar=*:0/15
# Persistent=true
# Calendar expressions:
# *:0/15 → every 15 min
# hourly → top of every hour
# daily → midnight
# Mon *-*-* 09:00:00 → Monday 9am
# *-*-01 00:00:00 → 1st of month
# Test calendar expression
systemd-analyze calendar "Mon *-*-* 09:00:00"
systemd-analyze calendar "*:0/15"
Debugging
# Why did it fail?
systemctl status myapp
journalctl -u myapp -n 50 --no-pager
# Dependency tree
systemctl list-dependencies myapp
# Analyze boot time
systemd-analyze blame
systemd-analyze critical-chain myapp.service
# Check unit file syntax
systemd-analyze verify /etc/systemd/system/myapp.service
# Show all properties
systemctl show myapp
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 · 237 lines · 44 tokens per session scan B 6f041d3c7e87
systemd-manager is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,301 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
analyzing-persistence-mechanisms-in-linux
Scan Linux systems for persistence mechanisms including crontab/systemd entries, LDPRELOAD injection, shell profile modifications (.bashrc, .profile), and SSH authorizedkeys backdoors, then correlate findings with auditd logs into an installation timeline. Use during incident response or threat hunting to detect or…
screen_lock
Password-lock the machine's screen while every process keeps running.
cml-admin
CML administration — user/group management, system info, licensing, resource monitoring. Use when creating CML users, checking license status, monitoring CML server resources, or auditing lab usage across teams.
drone_commands
Execute drone commands -- the AIPass CLI interface for all module operations.
system_status
Check system health -- disk usage, memory, running processes, uptime.
branch_health
Quick health check -- test counts and file stats for AIPass branches.