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 axel-pm/watch-n-learn --skill find-your-unknownsgit clone --depth 1 https://github.com/axel-pm/watch-n-learnWrote 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/axel-pm/watch-n-learn/find-your-unknowns)<a href="https://agentmods.dev/skills/axel-pm/watch-n-learn/find-your-unknowns"><img src="https://agentmods.dev/badge/skills/axel-pm/watch-n-learn/find-your-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/skills/axel-pm/watch-n-learn/find-your-unknowns"><img src="https://agentmods.dev/badge/skills/axel-pm/watch-n-learn/find-your-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.00171 | $0.01251 |
| Opus 5 | $0.00086 | $0.00626 |
| Sonnet 5 | $0.00034 | $0.00250 |
| Haiku 4.5 | $0.00017 | $0.00125 |
Grade A, and why
find-your-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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
find-your-unknowns
A more capable agent traverses more of the codebase, so it hits more decisions you never wrote down — and drifts. The fix is to find those decisions before the big run. Your prompt is a map; the codebase is the territory. This skill surfaces everywhere the territory holds something your map doesn't.
When to use vs. skip
- Use before a large, ambiguous, or architecture-shaping task, or when you (or the user) are new to this codebase or domain.
- Skip for a small, fully-specified change where the territory is already known — running the full battery would be ceremony.
Inputs
- A task/goal (what the user wants built or changed).
- A target repo or subsystem you can read.
- Optionally: reference code/mockups, and context about the user's taste, stage, and constraints.
Workflow
Don't blindly run all six. Pick by the kind of unknown in play (see table), run those, then
consolidate. Note the When column: only patterns 1–4 run during this scoping pass. Pattern 5
is an instruction you produce now but inject into the later build run; pattern 6 runs after the
build. Each pattern's full prompt template is in references/prompt-patterns.md.
| Kind of unknown | Pattern | When | Skip if |
|---|---|---|---|
| "I don't even know what I don't know here" | 1. Blind-spot pass | scoping | rarely — this is the anchor |
| Aesthetic / "know it when I see it" | 2. Brainstorm & prototype | scoping | the surface isn't primarily visual |
| Under-specified requirements | 3. Interview me | scoping | requirements are already crisp |
| An example is easier than a spec | 4. Reference — give it another map | scoping | you have no reference to point at |
| Deviations that only appear mid-build | 5. Implementation notes | build-time | never — it's a cheap always-on trail |
| Do I actually understand the result? | 6. Quiz me | post-build | you already own the result cold |
The six patterns (in the order you'd typically reach for them)
What ships with it
3 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.
- 11d ago First seen · 87 lines · 171 tokens per session scan A 565511309a3d
find-your-unknowns is a skill published in the GitHub repository axel-pm/watch-n-learn (9 stars, last pushed 1mo ago), licensed MIT. It adds 171 tokens to every session and 1,251 once invoked, about $0.0009 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
claude-code-eyes
Look at real hardware, screens, panels, and wiring on a desk or workbench through a camera, so Claude can SEE physical output that no unit test, log, or API can. Use whenever the user says "are you seeing this?", "olha isso", "look at this", "watch this", "can you see...", "check the camera", "look at the screen" /…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.