Borrowing it
Nothing to install: this file belongs to beydemirfurkan/todox. 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/beydemirfurkan/todox/main/AGENTS.mdgit clone --depth 1 https://github.com/beydemirfurkan/todoxWrote 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/beydemirfurkan/todox/agents-md)<a href="https://agentmods.dev/instructions/beydemirfurkan/todox/agents-md"><img src="https://agentmods.dev/badge/instructions/beydemirfurkan/todox/agents-md.svg" alt="Measured on agentmods" 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.03983 | $0.03983 |
| Opus 5 | $0.01992 | $0.01992 |
| Sonnet 5 | $0.00797 | $0.00797 |
| Haiku 4.5 | $0.00398 | $0.00398 |
Grade A, and why
todox 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 2d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices.
This block is written and re-added by next dev — verify at node_modules/next/dist/server/lib/generate-agent-files.js. Removing it from a diff only re-creates the uncommitted change; committing it with your work keeps the tree clean.
todox — agent rules
This file is read directly by Codex, Cursor, OpenCode and VS Code Copilot as
plain markdown (Codex has no @import support — @AGENTS.md is a Claude Code
extension). Claude Code reaches it through CLAUDE.md, which imports this
file.
Two-source rule (also captured in the PR template and
CONTRIBUTING.md): the "Domain rules" section below is mirrored verbatim inCONTRIBUTING.mdunder "The rules the codebase actually follows". A change to one is a change to the other; the duplication is intentional because Codex/Cursor will not follow a cross-file reference.
Sprint workflow
Think → Plan → Build → Review → Test → Ship → Reflect. No step is optional.
- Think. "Is this the right problem?" What the user said and what they meant can differ. Surface assumptions before committing to them.
- Plan. 2-3 alternatives. At minimum a minimal viable and an ideal architecture. Justify the recommendation; let the user pick.
- Build. Small, atomic commits. One commit = one logical change.
- Review. Read your own diff: scope creep, missing edge cases, silent
failures, security. Walk the
gstack-reviewchecklist. - Test. Run the affected tests. Write a regression test for new code.
- Ship. Open a PR; CI must be green. Verify production after merge.
- Reflect. What went well, what did not. One or two sentences.
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.
- 2d ago Changed · +16 lines · +269 tokens per session b7d147944093
- 6d ago First seen · 264 lines · 3,714 tokens per session scan A 4a1d261d904d
todox AGENTS.md is an instructions file published in the GitHub repository beydemirfurkan/todox (2 stars, last pushed yesterday), licensed MIT. It adds 3,983 tokens to every session, about $0.0199 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-31.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.