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 skills add FerroxLabs/wayland --skill business-ops-runbook-generatorgit clone --depth 1 https://github.com/FerroxLabs/waylandWrote 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/ferroxlabs/wayland/business-ops-runbook-generator)<a href="https://agentmods.dev/skills/ferroxlabs/wayland/business-ops-runbook-generator"><img src="https://agentmods.dev/badge/skills/ferroxlabs/wayland/business-ops-runbook-generator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ferroxlabs/wayland/business-ops-runbook-generator"><img src="https://agentmods.dev/badge/skills/ferroxlabs/wayland/business-ops-runbook-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00101 | $0.00934 |
| Opus 5 | $0.00051 | $0.00467 |
| Sonnet 5 | $0.00020 | $0.00187 |
| Haiku 4.5 | $0.00010 | $0.00093 |
Grade A, and why
business-ops-runbook-generator 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 8d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 8d ago First seen · 90 lines · 101 tokens per session scan A dd3625ea4f9a
business-ops-runbook-generator is a skill published in the GitHub repository FerroxLabs/wayland (604 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 101 tokens to every session and 934 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
feishu-troubleshoot
A Feishu troubleshooting tool with FAQs and diagnostic commands. Feishu is a collaboration platform with online documents and workplace services.
termcanvas-agent-sync-debugging
Diagnose TermCanvas agentmux nodes that fail to appear and terminal canvases that become janky, resize repeatedly, or show corrupted/unreadable xterm text as terminal count grows, plus duplicate terminal views created after a release relaunch. Use when a child agent is missing, restored terminals duplicate or move to…
investigate
Systematic debugging skill. Use when encountering a bug, test failure, unexpected behavior, or when asked to "investigate", "debug", "diagnose", or "figure out why". Enforces root-cause-first discipline with structured hypothesis tracking.
Debug (reproduce -> isolate -> fix)
Systematically diagnose and fix a bug instead of guessing.
error-collection
A structured record of confirmed engineering mistakes, their root causes, and checks that prevent them from returning. It uses evidence from real application behavior, not just successful builds.
flaky-test-triage
Use when a test passes and fails intermittently, behaves differently by order, machine, runtime, timing, or retry, or when the user asks to reduce test flakiness. Gather repeatable evidence, isolate nondeterminism, and repair the causal dependency without weakening test intent.