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 skills/gebruder/wirken/process-managernpx skills add gebruder/wirken --skill process-managergit clone --depth 1 https://github.com/gebruder/wirkenWrote 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/gebruder/wirken/process-manager)<a href="https://agentmods.dev/skills/gebruder/wirken/process-manager"><img src="https://agentmods.dev/badge/skills/gebruder/wirken/process-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 | $0.00008 | $0.00324 |
| Opus 5 | $0.00004 | $0.00162 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
process-manager 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.
What it actually says
Process Manager
Monitor and manage system processes.
List processes
- All:
ps aux - By CPU:
ps aux --sort=-%cpu | head -15 - By memory:
ps aux --sort=-%mem | head -15 - By name:
pgrep -af "<name>" - Tree:
pstree -p | head -40
Manage processes
- Kill by PID:
kill <pid> - Force kill:
kill -9 <pid> - Kill by name:
pkill <name> - Kill by port:
fuser -k <port>/tcp
Monitor
- Find by port:
ss -tlnp | grep <port> - Open files:
lsof -p <pid> | head -20 - File descriptors:
ls /proc/<pid>/fd | wc -l - Watch in real-time:
top -bn1 | head -20
Services (systemd)
- Status:
systemctl status <service> - Start/stop:
systemctl start|stop|restart <service> - Logs:
journalctl -u <service> --no-pager -n 30 - List running:
systemctl list-units --type=service --state=running
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 · 46 lines · 8 tokens per session scan A c0b50af65d63
process-manager is a skill published in the GitHub repository gebruder/wirken (170 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 324 once invoked, about $0.0000 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 skills, from other repositories
council
Run 8-persona Council validation on a feature/ADR, then auto-create a Linear ticket if score >= 8/10.
decompose
Decompose a MEGA ticket into component-scoped sub-issues on Linear, with dependency DAG and parallel execution plan.
generate-backlog
Scan codebase to generate MEGA backlog tickets (20-40 pts each). Maintains 400+ pts stock on Linear.
sync-plan
Cycle-aware bidirectional sync between plan.md and Linear. Discovers all cycle tickets, detects drift, updates markers.
fill-cycle
Analyze cycle capacity gap and propose backlog items to fill the sprint to 80% of proven velocity.
pr-guardian
STOA PR Guardian — advisory three-axis review (ADR compliance, security, AI code smell) with binary GO/NO-GO verdict + confidence. Never approves, never blocks merge.