Borrowing it
Nothing to install: this file belongs to traverse-framework/traverse. 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/traverse-framework/traverse/main/AGENTS.mdgit clone --depth 1 https://github.com/traverse-framework/traverseWrote 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/traverse-framework/traverse/agents-md)<a href="https://agentmods.dev/instructions/traverse-framework/traverse/agents-md"><img src="https://agentmods.dev/badge/instructions/traverse-framework/traverse/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/traverse-framework/traverse/agents-md"><img src="https://agentmods.dev/badge/instructions/traverse-framework/traverse/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.00598 | $0.00598 |
| Opus 5.5 | $0.00239 | $0.00239 |
| Sonnet 5.5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
traverse 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traverse — Agent Coordination
Canonical agent instructions (scope, structure, commands, style, governance) live in CLAUDE.md. This file holds only multi-tool coordination, per the org rule in traverse-framework/.github docs/ai-agent-hardening.md: claim before you code — one issue = one agent.
Agent Coordination
Before starting any work on an issue, run these pre-flight checks:
1. Check for Claude Code claim
gh issue view <NUMBER> --repo traverse-framework/traverse --json labels
If the labels include agent:claude → STOP. Report:
Issue #<NUMBER> is claimed by Claude Code. Choose a different ticket.
2. Check for Claude Code branch
git ls-remote --heads origin | grep "issue-<NUMBER>-"
If a claude/issue-<NUMBER>-* branch exists → STOP. Report:
A Claude Code branch already exists for issue #<NUMBER>. Choose a different ticket.
3. Claim the ticket (only if pre-flight passes)
# Add label (the ownership marker — the live org Project 1 has no Agent field)
gh issue edit <NUMBER> --repo traverse-framework/traverse --add-label "agent:codex"
# Get project item ID with bounded output
# Keep Project reads in bounded pages: large `project item-list` GraphQL
# requests can exceed GitHub's per-query cost limit even with account quota.
gh project item-list 1 --owner traverse-framework --format json --limit 100 \
--jq '.items[] | select(.content.number == <NUMBER>) | .id'
# Set Status → In Progress
gh project item-edit --project-id PVT_kwDOEbiBt84Bbyp1 \
--id <ITEM_ID> \
--field-id PVTSSF_lADOEbiBt84Bbyp1zhWglqM \
--single-select-option-id 47fc9ee4
Status option IDs for reference: Ready f75ad846, In Progress 47fc9ee4, Done 98236657, Blocked 294b89f5.
Active Technologies
- Rust 1.94+; host packages in TypeScript, Swift, Kotlin, and .NET + Cargo workspace, serde, semver, existing registry and embedder packages (524-production-app-readiness)
- host-owned verified artifact cache, append-only trace journal, host-owned file-backed DataStore v2 (524-production-app-readiness)
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 Changed · +2 lines · +33 tokens per session b22b65b58e88
- 1mo ago First seen · 52 lines · 565 tokens per session scan A dc7144767d0c
traverse AGENTS.md is an instructions file published in the GitHub repository traverse-framework/traverse (89 stars, last pushed 6d ago), licensed Apache-2.0. It adds 598 tokens to every session, about $0.0024 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).
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.