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/bacoco/useless-skills/radio-pausenpx skills add bacoco/useless-skills --skill radio-pausegit clone --depth 1 https://github.com/bacoco/useless-skillsWrote 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/bacoco/useless-skills/radio-pause)<a href="https://agentmods.dev/skills/bacoco/useless-skills/radio-pause"><img src="https://agentmods.dev/badge/skills/bacoco/useless-skills/radio-pause.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.00132 | $0.02259 |
| Opus 5 | $0.00066 | $0.01130 |
| Sonnet 5 | $0.00026 | $0.00452 |
| Haiku 4.5 | $0.00013 | $0.00226 |
Grade A, and why
radio-pause 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 5d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 243 lines · 132 tokens per session scan A cdd0e3324826
radio-pause is a skill published in the GitHub repository bacoco/useless-skills (2 stars, last pushed 4mo ago), with no licence file. It adds 132 tokens to every session and 2,259 once invoked, about $0.0007 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
skill-teilen
Reicht einen Skill, ein Plugin oder eine Vorlage (CLAUDE.md, settings.json, Prompt) in die SKAILE Community Skill-Library ein. Nutzen wenn der User sagt "teile meinen Skill", "teile meine CLAUDE.md", "teile meine Vorlage", "lade meinen Skill in die Community hoch", "reiche meinen Skill ein", "skill teilen" oder "in…
show-and-share
Schreibt einen fertigen Show-&-Share-Post für die SKAILE Community. Nutzen wenn der User sagt "schreib mir einen Show & Share Post", "stelle meinen Skill vor", "Post für meinen Skill/meine Vorlage", "schreib einen Post zu dem was ich gebaut habe", oder direkt nachdem ein Skill mit skill-teilen eingereicht wurde.
readme-pro
Schreibt oder verbessert ein README für das aktuelle Projekt. Nutzen wenn der User "schreib mir ein README", "dokumentier das Projekt" oder "readme-pro" sagt.
flow-next-interview
In-depth Q&A to refine a spec, task, or spec file before building. Use when asked to flesh out, refine, or interrogate requirements.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.