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.
git clone --depth 1 https://github.com/baizhiyuan/finding-unknowns-skillWrote 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/commands/baizhiyuan/finding-unknowns-skill/finding-unknowns)<a href="https://agentmods.dev/commands/baizhiyuan/finding-unknowns-skill/finding-unknowns"><img src="https://agentmods.dev/badge/commands/baizhiyuan/finding-unknowns-skill/finding-unknowns/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/commands/baizhiyuan/finding-unknowns-skill/finding-unknowns"><img src="https://agentmods.dev/badge/commands/baizhiyuan/finding-unknowns-skill/finding-unknowns.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.00016 | $0.00162 |
| Opus 5.5 | $0.00006 | $0.00065 |
| Sonnet 5.5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
finding-unknowns 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 1mo 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
finding-unknowns
Dispatch command for the finding-unknowns skill.
Dispatch
- Read the full skill instructions from
skills/finding-unknowns/SKILL.mdin this plugin (locate it under the active plugin root or~/.claude/skills/finding-unknowns/SKILL.mdfor manual installs). - Follow that SKILL.md exactly, starting at Phase 0 (quadrant routing), treating the user's arguments as the task description:
$ARGUMENTS
If no arguments were given, ask the user what task or area they want to probe, then begin Phase 0.
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.
- 1mo ago First seen · 23 lines · 16 tokens per session scan A d4c7ee563c7b
finding-unknowns is a command published in the GitHub repository baizhiyuan/finding-unknowns-skill (5 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 162 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
obsidian-recap
Summarize a time period from the vault - today, week, or month.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
elite-review
Run an elite, high-scrutiny Claude review against the current git workspace.
preview
Dry-run llm-redact detection on sample text — see exactly what would be redacted.