Borrowing it
Nothing to install: this file belongs to initxy/noeta. 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/initxy/noeta/main/AGENTS.mdgit clone --depth 1 https://github.com/initxy/noetaWrote 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/initxy/noeta/agents-md)<a href="https://agentmods.dev/instructions/initxy/noeta/agents-md"><img src="https://agentmods.dev/badge/instructions/initxy/noeta/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/initxy/noeta/agents-md"><img src="https://agentmods.dev/badge/instructions/initxy/noeta/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.01870 | $0.01870 |
| Opus 5.5 | $0.00748 | $0.00748 |
| Sonnet 5.5 | $0.00374 | $0.00374 |
| Haiku 4.5 | $0.00187 | $0.00187 |
Grade A, and why
noeta 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Communication
- Keep answers concise and direct; lead with the conclusion and the next step.
- Don't add unrelated explanation; when unsure, state your assumptions and the risks.
- Don't narrate what you're about to do or recap what you just did; report only what changes what the reader does next.
- Conversation may happen in whatever language the other side uses; everything committed to the repo (see Language) is English.
Language
- All repository artifacts are written in English: docs (
CONTEXT.md,docs/adr/,docs/specs/), code comments, and identifiers. The only exceptions are the Chinese mirrors —README.zh-CN.md,docs/zh/**,docs/releasing.zh.md. - Keep technical terms in their canonical English form and spell them consistently throughout: code identifiers (function / class / file / variable names), API / library / tool / command names, file paths, and fixed architecture terms (module, interface, seam, adapter, deep module, etc.). Don't invent alternate names or switch between synonyms.
- Write clear, idiomatic English prose — not word-for-word translation from another language.
- Pick one spelling per term and use it everywhere; don't mix variants.
- Naming is enforced by
scripts/lint-naming.py(inmake check); the banned names and the canonicalTask/root_task_idare inCONTEXT.md'sNaming:entries.
Context / ADR
- Read
CONTEXT.mdfirst whenever you touch domain concepts, system boundaries, or stable conventions. A package with its ownAGENTS.mdkeeps its module-only concepts there. - Read
docs/adr/(start atdocs/adr/index.md) first whenever a long-term architecture trade-off is involved; never rely on an ADR markedsuperseded, and read the ADRs listed under itsRefined by. - Code is the single source of truth for "what is." When docs and code disagree, trust the code and fix the docs.
- One fact, one home: never state the same fact in two docs — link instead. A change that invalidates a
CONTEXT.mdentry or ADR updates it in the same task. - Write docs lean: a
CONTEXT.mdorAGENTS.mdline exists only if code can't tell an agent the same thing quickly; point at code by repo path instead of restating it. An ADR only for a shipped decision that is costly to reverse; changing one is a new ADR that refines or supersedes it, never an amendment in place.scripts/check-docs.shholds the budgets and formats — trim, don't raise them. When unsure, don't write it. - Code comments carry only constraints the code can't show — never a
docs/specs/reference (one-shot artifacts). Code needn't cite ADRs; where a comment names one it is plain prose, not a contract (docs/adr/006-doc-code-link-direction.md). - Archived specs (
docs/specs/archive/) are construction history — never read them as a description of the current system.
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 · +1 lines · +57 tokens per session 39146259887d
- 3d ago Changed · +36 lines · +858 tokens per session ece4447a4158
- 1mo ago Changed · -3 tokens per session 2d1e828d79d8
- 1mo ago Changed · +30 tokens per session 2706691f119b
- 2mo ago First seen · 43 lines · 928 tokens per session scan A 6f0825cacb3c
noeta AGENTS.md is an instructions file published in the GitHub repository initxy/noeta (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,870 tokens to every session, about $0.0075 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.