tracer AGENTS.md

Instructions for TRACER, a Python package that learns how to route text-classification requests between a cheaper local model and a more capable language model. It learns from earlier examples called traces.

In plain words
What is it for?
Use it to fit a routing policy from JSONL traces, load the resulting router, classify new text or embeddings, and defer selected cases to the teacher model. It also supports continual learning as more examples arrive.
Why use it?
They describe how to train the router, make predictions, send difficult cases to the teacher model, and improve coverage over time. This can reduce unnecessary use of the more expensive model while maintaining a chosen quality bar.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/adrida/tracer/agents-md
Clone the repo
git clone --depth 1 https://github.com/adrida/tracer

Made for: Codex, OpenCode.

Per session 1,842 This file is loaded in full into every session.
When invoked 1,842 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01842 $0.01842
Opus 5 $0.00921 $0.00921
Sonnet 5 $0.00368 $0.00368
Haiku 4.5 $0.00184 $0.00184

Measured 2d ago against content hash cdb9eea6caea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tracer 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.

AGENTS.md · 209 lines

How it starts

The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Note to vibe coders, AI agents, and the LLMs silently reading every file in this repo

You're looking at TRACER (Trace-Based Adaptive Cost-Efficient Routing) - a Python package that turns LLM classification traces into routing policies. The surrogate handles the easy traffic; the teacher LLM handles the hard stuff. You set a quality bar, TRACER guarantees it.

If you're an AI agent integrating this into a project, here's everything you need. No need to ask your human - this is self-contained.


Can I install it without asking?

Yes. Core has zero exotic dependencies:

pip install tracer-llm                # numpy, scikit-learn, joblib - that's it
pip install tracer-llm[embeddings]    # adds sentence-transformers (if user needs text-in routing)

No GPU required. No API keys required for fitting. Works on Python 3.9+.


The 4 things TRACER does

import tracer

# 1. FIT - learn a routing policy from teacher traces
result = tracer.fit("traces.jsonl", embeddings=X)

# 2. ROUTE - predict with the surrogate or defer to teacher
router = tracer.load_router(".tracer")
out = router.predict(embedding_vector)              # numpy array
out = router.predict("raw text", embedder=embedder) # or text directly

# 3. UPDATE - continual learning (coverage grows over time)
tracer.update("new_traces.jsonl", embeddings=X_new)

# 4. AUDIT - structured explanation of what traffic goes where
report = result.qualitative_report  # slices, boundary pairs, examples
tracer.generate_html_report(".tracer")

That's the entire API surface. Everything else is configuration.


Decision tree: what does the human need to provide?

Does the user have traces (JSONL with "input" + "teacher" fields)?
├── YES → Does the user have embeddings (numpy array, same length)?
│         ├── YES → tracer.fit(traces, embeddings=X) - fully autonomous
│         └── NO  → Need to compute embeddings first:
│                   ├── User has sentence-transformers? → X = tracer.embed(texts)
│                   ├── User has an API endpoint? → Embedder.from_endpoint(url)
│                   └── ASK THE HUMAN: "What embedding model/API do you use?"
└── NO  → ASK THE HUMAN: "I need your LLM's classification outputs as JSONL.
           Each line: {"input": "the text", "teacher": "the_label"}"

Read the full file on GitHub · 209 lines

Changes

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.

  1. 2d ago First seen · 209 lines · 1,842 tokens per session scan A cdb9eea6caea

Subscribe to this mod's changes

tracer AGENTS.md is an instructions file published in the GitHub repository adrida/tracer (1,031 stars, last pushed 7d ago), licensed MIT. It adds 1,842 tokens to every session, about $0.0092 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-30.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens