Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/yogasw/wick/agent-resource-guard)<a href="https://agentmods.dev/skills/yogasw/wick/agent-resource-guard"><img src="https://agentmods.dev/badge/skills/yogasw/wick/agent-resource-guard.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.00231 | $0.09624 |
| Opus 5 | $0.00115 | $0.04812 |
| Sonnet 5 | $0.00046 | $0.01925 |
| Haiku 4.5 | $0.00023 | $0.00962 |
Grade A, and why
agent-resource-guard 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 738 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Resource Guard
Wick spawns agents (claude, codex, gemini) as child processes, and those agents spawn their own children — MCP servers, tool subprocesses, browsers. This subsystem bounds what all of that may consume, and measures what it actually does consume.
It is not only memory. Memory is the part that kills, so it gets the deepest treatment; CPU, block-IO, and process count are bounded too, and all four are measured. The name "memory guard" survives in config keys for compatibility — read it as "resource guard".
The one idea to keep
The kernel enforces. Wick observes and explains.
Every design decision below follows from that. A userspace sampler cannot win against a browser that allocates a gigabyte between two ticks, so wick never tries to kill on a sample. It asks the kernel to enforce a ceiling, then reads back what happened so a human gets a sentence instead of exit code 137.
Easy to read backwards
These four have already been misread — twice from the skill's own description, before it said this. If you are answering a question about any of them, quote this section rather than paraphrasing:
| Sounds like | Actually means |
|---|---|
| "measure writes nothing" | Writes no limits. Records usage in full — that is the mode's purpose. |
| "swap must stay off" | Not about OOM-killer predictability. With swap, the process never dies; it thrashes and holds its slot forever. |
| "the guard ships off by default" | Enforcement is off. Usage history is on and independent of the mode. |
| "unavailable without systemd" | Limits still apply without systemd — the cgroupfs backend enforces them. What systemd adds is the ability to name an OOM kill. And measurement, admission, the Resources page, and oom_score_adj never needed either. See the degradation table. |
The shared shape: measurement and enforcement are separate axes. Nearly every misreading here comes from collapsing them into one.
Why this exists
Production wick was being OOM-killed. Not from a leak in wick — an agent or a tool subprocess would balloon (usually a browser or a large file read), and because every one of them was a child of wick inside wick's own cgroup, the kernel's OOM killer took wick down with them.
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.
- 6d ago First seen · 738 lines · 231 tokens per session scan A 88149f41b61d
agent-resource-guard is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed 2d ago), licensed MIT. It adds 231 tokens to every session and 9,624 once invoked, about $0.0012 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
specification-writing
Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
golden-rss
Use when testing the rss golden build.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
omh-code-review
This is a Hermes-native code-review workflow skill.