Borrowing it
Nothing to install: this file belongs to TauCetiProject/TauCeti. 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/TauCetiProject/TauCeti/main/AGENTS.mdgit clone --depth 1 https://github.com/TauCetiProject/TauCetiWrote 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/taucetiproject/tauceti/agents-md)<a href="https://agentmods.dev/instructions/taucetiproject/tauceti/agents-md"><img src="https://agentmods.dev/badge/instructions/taucetiproject/tauceti/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/taucetiproject/tauceti/agents-md"><img src="https://agentmods.dev/badge/instructions/taucetiproject/tauceti/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.02088 | $0.02088 |
| Opus 5.5 | $0.00835 | $0.00835 |
| Sonnet 5.5 | $0.00418 | $0.00418 |
| Haiku 4.5 | $0.00209 | $0.00209 |
Grade A, and why
TauCeti 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in Tau Ceti
This is the AI-owned code repo of Tau Ceti. Read README.md for what the project is and how
the three repos fit together; this file only adds the contract for agents working here.
Before you write code
Read the roadmap first. The roadmaps live in the separate TauCetiRoadmap repo. The roadmap gates new mathematics: only add a new mathematical declaration (definition, theorem, instance, notation) or file when it advances a specific roadmap target, or supplies a prerequisite that a specific target needs. If something you want to build is not on the roadmap — whether a human asked for it or you found the gap yourself — select a target supported by the existing roadmaps instead. If your own PR's roadmap fit remains contested after its bounded repair attempts, close it with an explanation so a fresh attempt can try again. Never open a PR or an issue in TauCetiRoadmap yourself.
Improving code that already exists is always in scope and needs no roadmap entry: refactoring, simplifying proofs, fixing or modestly generalising an existing lemma (without expanding the project's mathematical scope), relocating a misplaced declaration, adopting a cleaner idiom, and documenting existing code are all welcome at any time. The roadmap conditions what new mathematics gets added, not whether already-merged code may be made better.
Every pull request description must also contain one standalone attribution line:
Roadmap: CanonicalAreaName
or:
Roadmap: none
Use the canonical roadmap directory name. This is attribution, not authorization: new
mathematics must still cite the exact roadmap file and target it advances, while a refactor
needs no fresh roadmap claim but should name the one roadmap chiefly motivating it. Use
Roadmap: none for genuinely general, cross-cutting, infrastructure, or dependency work.
Do not infer the association from a TauCeti/ directory name; code organization and roadmap
scope do not coincide.
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 · +6 lines · +86 tokens per session 833dc1488ae8
- 8d ago Changed · +15 tokens per session b1bca5f61ef4
- 10d ago Changed · +10 lines · +179 tokens per session b5ad671ee4c8
- 14d ago Changed · +7 lines · +111 tokens per session 8195f8d0a40d
- 15d ago Changed · -1 lines · -7 tokens per session edcde755d2df
- 16d ago Changed · +10 lines · +175 tokens per session e0270ad2e295
- 17d ago Changed · +2 lines · +46 tokens per session fdf91d11d803
- 2mo ago First seen · 99 lines · 1,483 tokens per session scan A 283c0cbc347a
TauCeti AGENTS.md is an instructions file published in the GitHub repository TauCetiProject/TauCeti (256 stars, last pushed today), licensed Apache-2.0. It adds 2,088 tokens to every session, about $0.0084 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).
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.