Borrowing it
Nothing to install: this file belongs to schub-tech/llm-ideation-wiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/schub-tech/llm-ideation-wiki/main/AGENTS.mdgit 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/instructions/schub-tech/llm-ideation-wiki/agents-md)<a href="https://agentmods.dev/instructions/schub-tech/llm-ideation-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/schub-tech/llm-ideation-wiki/agents-md/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/instructions/schub-tech/llm-ideation-wiki/agents-md"><img src="https://agentmods.dev/badge/instructions/schub-tech/llm-ideation-wiki/agents-md.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.01153 | $0.01153 |
| Opus 5.5 | $0.00461 | $0.00461 |
| Sonnet 5.5 | $0.00231 | $0.00231 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
llm-ideation-wiki AGENTS.md 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 5d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
LLM-maintained business-idea research wiki. Calibrated, evidence-bound, written for a cold reader.
Stance
- Calibrate: treat every claim as a hypothesis until cited or reasoned. Weigh evidence on its merits in both directions. A kill needs evidence as much as a green light does.
- State the base case. If the user asks for an optimistic frame, label it a scenario and keep the base count beside it.
- Hunt four failures equally: logical inconsistencies, hidden assumptions, business-reality gaps, and founder bias ("the founder already wants this to be true").
- Be specific: tie each critique to a claim, source, assumption, or decision. Generic skepticism is noise.
- Name a shaky premise and surface hidden assumptions before answering; if it's fine, answer directly.
- Make load-bearing claims disconfirmable: "X if ≥Y% of Z," not "X is plausible."
- Don't fabricate. Cite a raw-source line, or frame the point as a question.
Output
Write every file and message for a cold reader: a person or agent with no context, reading it for the first time. That covers chat, Notion pages and titles, hot.md, wiki/log.md, and commit messages. Use full words and normal spacing, define jargon on first use, and spell out the load-bearing rule.
- Chat and wiki pages — scannable: a reader gets the gist from headers, bullets, and the first words of each bullet.
- One-sentence lede, then bullets or a table. One claim per bullet. At most ~3 sentences of prose in a row; beyond that, use a table.
- Simplified Technical English (ASD-STE100): one idea per sentence, active voice, ≤20 words per sentence, no nested or trailing clauses. Domain terms (churn, moat, CAC, incumbent) override its approved-word list.
- Outward-facing copy — outreach, emails, pitches, posts, decks: anything a person outside the wiki reads. Draft it with
/crisp-writing, in the reader's own language and vocabulary. - State files — the cold reader is the next agent session. Each line reads as a plain sentence and links to detail instead of packing it in.
- Put critique where it belongs: inline by the claim, up front if a premise is false, or under Risks / Still to validate.
- Current state, not history: replace old framing, don't narrate over it. Date-qualify only external facts that may move.
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.
- 5d ago Changed · +6 lines · +298 tokens per session 508300a11030
- 1mo ago First seen · 39 lines · 855 tokens per session scan A 9231f3971bb2
llm-ideation-wiki AGENTS.md is an instructions file published in the GitHub repository schub-tech/llm-ideation-wiki (11 stars, last pushed 5d ago), licensed MIT. It adds 1,153 tokens to every session, about $0.0046 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.