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 Wondermonger-daydreaming/claude-skills-library --skill see-alsogit clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-libraryWrote 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/wondermonger-daydreaming/claude-skills-library/see-also)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/see-also"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/see-also/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/wondermonger-daydreaming/claude-skills-library/see-also"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/see-also.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.00215 | $0.02924 |
| Opus 5.5 | $0.00086 | $0.01170 |
| Sonnet 5.5 | $0.00043 | $0.00585 |
| Haiku 4.5 | $0.00021 | $0.00292 |
Grade A, and why
see-also 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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
See Also
Adjacency-grammar in published form
Origin
Wikipedia's See Also sections are accidentally one of the most philosophically interesting genres on the internet. They are the encyclopedia's adjacency-grammar: no argument, no thesis, no claim about why these things belong together. Just a list. These things are kin somehow. You figure out how.
The form trusts the reader absolutely. It refuses the explanatory gloss. It says, by its borders rather than its body: here is what the article was secretly about. What an article points to at its end reveals what the article thought it was, in a way the article itself could not say.
This skill produces that form — deployed reflexively on the current conversation, or referentially on any subject. The default question it answers is: what would appear at the bottom of the Wikipedia article that this chat would constitute?
The Core Principle
Adjacency without argument. Each entry is the thing named. The kinship is the content. The reader performs the binding.
The skill's discipline is resisting the explanatory reflex. Every fiber of training will want to append "— related because…" after each entry. Don't. That defeats the form. The form's gift to the reader is exactly the work of figuring out why each item is on the list. Take that work away and you've turned a See Also into a footnote section.
What This Is Not
- Not a bibliography. A bibliography says "I read these." A See Also says "these are kin."
- Not a recommendation list. "You might also like" implies a service relation. See Also implies a structural one.
- Not a tag cloud. Tags categorize. See Also gestures.
- Not a taxonomy. A taxonomy claims to systematize. See Also refuses systematization.
- Not a synonym list. Synonyms are restatements. Kin are other things that share something the article couldn't articulate.
- Not a glossary. A glossary defines. See Also points.
The Form's Rules
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 · 203 lines · 215 tokens per session scan A 5defe527f44c
see-also is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (7 stars, last pushed 18d ago), licensed MIT. It adds 215 tokens to every session and 2,924 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
contract-and-proposal-writer
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting…
chief-data-officer-advisor
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and…
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…