Borrowing it
Nothing to install: this file belongs to phenomenoner/ai-agent-thinkroom. 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/phenomenoner/ai-agent-thinkroom/main/AGENTS.mdgit clone --depth 1 https://github.com/phenomenoner/ai-agent-thinkroomWrote 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/phenomenoner/ai-agent-thinkroom/agents-md)<a href="https://agentmods.dev/instructions/phenomenoner/ai-agent-thinkroom/agents-md"><img src="https://agentmods.dev/badge/instructions/phenomenoner/ai-agent-thinkroom/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/phenomenoner/ai-agent-thinkroom/agents-md"><img src="https://agentmods.dev/badge/instructions/phenomenoner/ai-agent-thinkroom/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.00362 | $0.00362 |
| Opus 5.5 | $0.00145 | $0.00145 |
| Sonnet 5.5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
ai-agent-thinkroom 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 2mo 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
Repository instructions
Authority
Implement docs/specification.md. Preserve the product semantics in thinkroom_ai_think_tank_product_concept.md. Do not silently reduce P0 scope or release gates.
Engineering method
- Use strict RED → GREEN → REFACTOR for behavior changes.
- Keep domain and application layers independent of FastAPI, SQLite, subprocess, provider SDKs, CLI, and MCP.
- Prefer small cohesive modules and explicit typed ports over framework magic.
- Treat model output as untrusted input: validate schemas, bound retries, and preserve evidence verification status.
- Never use
shell=Trueor interpolate user input into commands. - Do not add distributed infrastructure without an observed need.
- Keep production defaults loopback-only and fail closed on unsafe public binding while authentication is absent.
Required gates
The implementation is not complete until these pass from a clean checkout:
uv lock --check
uv sync --locked --all-extras --dev
uv run ruff format --check .
uv run ruff check .
uv run mypy src
uv run pytest
python3 scripts/build_release.py --out-dir /absolute/external/empty/dist
Add package-install and native production-process smoke tests/scripts. A production wheel release must include requirements-production.txt, uv.lock, and the flat asset verify_locked_runtime.py; install hash-locked dependencies first and the wheel with --no-deps. Docker is an operator-owned reference integration, not part of the v0.2 native release claim. Docker availability or smoke status does not gate the native release.
Claim discipline
A scripted backend proves orchestration, not model quality. A real provider smoke proves integration, not correctness of the research. SQLite release support is single-instance only.
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.
- 2mo ago First seen · 36 lines · 362 tokens per session scan A 6ef3cb3a98e3
ai-agent-thinkroom AGENTS.md is an instructions file published in the GitHub repository phenomenoner/ai-agent-thinkroom (2 stars, last pushed 24d ago), licensed MIT. It adds 362 tokens to every session, about $0.0014 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).
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.