Borrowing it
Nothing to install: this file belongs to paultyng/ideate. 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/paultyng/ideate/main/AGENTS.mdgit clone --depth 1 https://github.com/paultyng/ideateWrote 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/paultyng/ideate/agents-md)<a href="https://agentmods.dev/instructions/paultyng/ideate/agents-md"><img src="https://agentmods.dev/badge/instructions/paultyng/ideate/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/paultyng/ideate/agents-md"><img src="https://agentmods.dev/badge/instructions/paultyng/ideate/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.00641 | $0.00641 |
| Opus 5.5 | $0.00256 | $0.00256 |
| Sonnet 5.5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
ideate 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 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Cross-agent guidance for any AI agent (Claude Code, future runners, external orchestrators) working on the Ideate codebase. Claude-specific context lives in CLAUDE.md; this file captures principles that apply regardless of which agent is at the keyboard.
Build features as MCP tools first, UI second
When adding a new capability, the default surface is an MCP tool on the orchestrator (root orchestrator) MCP server, not a UI control.
Why:
- The orchestrator is the most-used surface — most workflows already start there. A tool exposed there reaches the user without a context switch.
- Tools compose: the orchestrator can chain
rename_idea,add_resource_by_slug,update_idea_by_sluginto a single operation. UI buttons can't. - Tools are scriptable. A workflow that lives only in the UI can't be triggered from a session, a hook, or another agent.
- Less code: an MCP tool is a handler + a schema. A UI feature adds React state, routing, styling, Playwright tests, and the back-and- forth between frontend and backend.
The default lift is therefore: pick the right MCP surface (per-idea vs orchestrator), wire the tool, write the test. Stop there.
When to add UI
Only when the operation cannot reasonably be driven from a conversation. The clearest case is starting an interactive session — the user has to physically attach to a PTY, so a button is unavoidable. Other cases that have justified UI in the past:
- Live terminal interaction (the xterm canvas is the UI).
- Markdown / diff review surfaces — the human reads a rendered diff and clicks comment widgets that don't translate to text.
- Status indicators that need to stay visible across navigations (footer toggles, session bar chips).
If a feature is a one-shot data mutation ("rename this idea", "drop old reviews", "add a tag") it belongs in MCP. If it's a continuous visual state ("show me the agent's terminal", "render this diff"), it belongs in the UI.
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 · 64 lines · 641 tokens per session scan A 751b10b7823f
ideate AGENTS.md is an instructions file published in the GitHub repository paultyng/ideate (9 stars, last pushed 1mo ago), licensed MIT. It adds 641 tokens to every session, about $0.0026 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 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.