Borrowing it
Nothing to install: this file belongs to tyler-mitchell/type-atlas. 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/tyler-mitchell/type-atlas/main/AGENTS.mdgit clone --depth 1 https://github.com/tyler-mitchell/type-atlasWrote 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/tyler-mitchell/type-atlas/agents-md)<a href="https://agentmods.dev/instructions/tyler-mitchell/type-atlas/agents-md"><img src="https://agentmods.dev/badge/instructions/tyler-mitchell/type-atlas/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/tyler-mitchell/type-atlas/agents-md"><img src="https://agentmods.dev/badge/instructions/tyler-mitchell/type-atlas/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.05987 | $0.05987 |
| Opus 5.5 | $0.02395 | $0.02395 |
| Sonnet 5.5 | $0.01197 | $0.01197 |
| Haiku 4.5 | $0.00599 | $0.00599 |
Grade A, and why
type-atlas 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Guidelines:
- Scripting Language: TypeScript script files
- Programming Style: Functional Programming
- Comments: bare minimum, caveman prose. Say the thing in the fewest plain words that still carry it — short clauses, no essays, no story of how the code got here. A comment earns its line only when the code cannot state the constraint itself. This binds every comment you write or edit; it is never an activity of its own, and never a reason to touch comments the work did not already touch.
Shared Agent Workflow
- Daily branch:
main - Bumpy base branch:
release - Generated version PR:
bumpy/version-packages
The human owns the checked-out branch. Agents never create, switch, rename, delete, reset, or replace branches unless the human requests that exact operation. If another branch is checked out, continue there and report the difference.
Work and commit on the checked-out branch. Stage only task-owned files. If the
index already contains another agent’s files, commit task-owned paths only and
leave the other staged entries untouched with
git commit --only -- <task-owned paths>. Never delete .git/index.lock; wait
for the other Git operation to finish.
commit authorizes a local commit only. push authorizes the checked-out
branch and includes every unpushed commit already on it; report that complete
commit set before pushing. Consumer-visible package changes include one
maintained Bumpy bump file. Agents never create task branches or worktrees.
Bump lifecycle
Bumps are authored during change development, never reconstructed just before
release. The first consumer-visible commit for a logical change creates one
bump file through vp run release add; later commits for that same change
update the same file. An unrelated logical change gets its own bump file.
Commit the implementation, tests, generated consumer docs, and bump file
together. Follow .skills/add-change/SKILL.md for the exact command, bump
level, package attribution, and changelog text. Use patch for compatible fixes,
minor for compatible capabilities, and major for breaking public contracts.
Name only directly changed packages; Bumpy owns fixed-group and dependency
propagation. Root shared changes name every affected public package explicitly.
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 · 175 lines · 5,987 tokens per session scan A d33b149c4c3f
type-atlas AGENTS.md is an instructions file published in the GitHub repository tyler-mitchell/type-atlas (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 5,987 tokens to every session, about $0.0239 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.