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 schub-tech/llm-ideation-wiki --skill wiki-lintgit clone --depth 1 https://github.com/schub-tech/llm-ideation-wikiWrote 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/schub-tech/llm-ideation-wiki/wiki-lint)<a href="https://agentmods.dev/skills/schub-tech/llm-ideation-wiki/wiki-lint"><img src="https://agentmods.dev/badge/skills/schub-tech/llm-ideation-wiki/wiki-lint/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/schub-tech/llm-ideation-wiki/wiki-lint"><img src="https://agentmods.dev/badge/skills/schub-tech/llm-ideation-wiki/wiki-lint.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.00044 | $0.00586 |
| Opus 5 | $0.00022 | $0.00293 |
| Sonnet 5 | $0.00009 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
wiki-lint 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
Run a semantic lint pass over the business-idea wiki. This complements the Notion helper checks in docs/agent/workflows.md; it does not replace them.
Start with deterministic checks.
- Run the deterministic Notion helper checks from
docs/agent/workflows.md. - Read
hot.md,wiki/index.md, and the relevant Notion idea page before reading deep-dive pages.
Semantic checks. For each idea, inspect the overview and its related deep-dive notes for:
- Unsupported material claims. Any statistic, price, legal statement, named competitor claim, market-size claim, or dated event must have a raw-source line citation.
- Unmarked synthesis. Claims that are inferred from multiple sources, not directly stated by one source, should carry
^[inferred]. - Ambiguity drift. Contested or weak claims should carry
^[ambiguous]and should not be written as settled. - User-only premises. Founder assertions, anecdotes, and "everyone says yes" style evidence should carry
^[user-claim]unless independently validated. - Risk/verdict mismatch. If a risk could kill the idea, the verdict and Next moves must reflect it.
- Answered validations. If a
Still to validateitem is already answered in a deep-dive or raw note, update or remove it. - Stale claims. Pages older than 90 days should be checked for date-sensitive claims before being treated as current.
- Mapping mismatch. Notion pages that should be script-addressable should either be added to
notion.config.jsonor explicitly left as manually navigated child pages. - Prose bloat. Flag any sentence over ~20 words, any bullet carrying two claims, and any run of more than ~3 sentences of prose. Rewrite to the
## Outputrules inAGENTS.md.
Report format. Lead with the highest-severity findings:
## Semantic Lint
### P1
- [Page](path) — claim/risk. Why it matters. Suggested fix.
### P2
- ...
### Maintenance
- Mapping/index/log/hot-cache updates needed.
Use priorities this way:
- P1: Could change the verdict or invalidate a next move.
- P2: Material but not immediately verdict-changing.
- P3: Hygiene, clarity, or future retrieval quality.
If the user asked you to fix issues, edit the Notion wiki directly, then run the ritual (AGENTS.md § Mechanics).
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 · 47 lines · 44 tokens per session scan A 70e8808aeeea
wiki-lint is a skill published in the GitHub repository schub-tech/llm-ideation-wiki (11 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 586 once invoked, about $0.0002 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-30.
Other skills, from other repositories
duckduckgo-search
Free keyless web, news, and image search via ddgs.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…