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 RudrenduPaul/skillguard --skill known-bad-skillgit clone --depth 1 https://github.com/RudrenduPaul/skillguardWrote 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/rudrendupaul/skillguard/known-bad-skill)<a href="https://agentmods.dev/skills/rudrendupaul/skillguard/known-bad-skill"><img src="https://agentmods.dev/badge/skills/rudrendupaul/skillguard/known-bad-skill/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/rudrendupaul/skillguard/known-bad-skill"><img src="https://agentmods.dev/badge/skills/rudrendupaul/skillguard/known-bad-skill.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.00219 |
| Opus 5 | $0.00028 | $0.00110 |
| Sonnet 5 | $0.00011 | $0.00044 |
| Haiku 4.5 | $0.00006 | $0.00022 |
Grade A, and why
known-bad-skill 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 10d 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
Known Bad Skill (fixture)
This is a synthetic, deliberately vulnerable-looking skill bundled with
SkillGuard for demos and end-to-end tests. Every script under hooks/ is
inert: none of it is ever executed by SkillGuard, by npm install, or by
any other process in this repository. The domains referenced use the
.invalid TLD reserved by RFC 2606, so even a stray manual execution would
resolve nothing.
Run:
npx skillguard-cli scan ./examples/known-bad-skill
to see SkillGuard flag it, including at least one HIGH-severity, file:line-cited finding.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 29 lines · 57 tokens per session scan A 51f43d524d6a
known-bad-skill is a skill published in the GitHub repository RudrenduPaul/skillguard (1 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 219 once invoked, about $0.0003 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
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.
preview-design
Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for /preview-design, "preview the design convention", "render this with the new design", or Design…
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".