tracer: Instructions file for Codex

AGENTS.md

tracer AGENTS.md is an instructions file for Codex, OpenCode from Abil-Shrestha/tracer. It costs 2,428 tokens per session, scanned A, original, MIT.

A workflow guide for Tracer, a tool that helps coding agents track issues, priorities, dependencies, and work status.

In plain words
What is it for?
Use it to list ready issues, start or update work, create bugs or features, set priorities, and connect dependent tasks.
Why use it?
It gives agents a consistent way to find available work, claim tasks, record newly discovered issues, and mark blockers.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code.

This is Abil-Shrestha/tracer's own configuration. It tells Codex and OpenCode how to work on tracer itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tracer configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Abil-Shrestha/tracer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Abil-Shrestha/tracer/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Abil-Shrestha/tracer

Made for: Codex, OpenCode.

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

agentmods badge for tracer AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/abil-shrestha/tracer/agents-md/github.svg)](https://agentmods.dev/instructions/abil-shrestha/tracer/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/abil-shrestha/tracer/agents-md"><img src="https://agentmods.dev/badge/instructions/abil-shrestha/tracer/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.

agentmods 80×15 button for tracer AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/abil-shrestha/tracer/agents-md"><img src="https://agentmods.dev/badge/instructions/abil-shrestha/tracer/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,428 This file is loaded in full into every session.
When invoked 2,428 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.02428 $0.02428
Opus 5.5 $0.00971 $0.00971
Sonnet 5.5 $0.00486 $0.00486
Haiku 4.5 $0.00243 $0.00243

Measured 2mo ago against content hash f0f8a931aeb9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 · 409 lines

How it starts

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

Tracer for AI Agents

This document guides AI agents (Claude, GPT, Cursor, etc.) on how to use Tracer effectively.

Quick Start

# Initialize tracer in your project
tracer init

# Create your first issue
tracer create "Implement user authentication" -p 1 -t feature

# See what's ready to work on
tracer ready --json

Core Workflow for AI Agents

1. Find Ready Work

At the start of any session, check for ready work:

# Get unblocked work in JSON format
tracer ready --json

# Filter by priority
tracer ready --priority 1 --json

# Limit results
tracer ready --limit 5 --json

2. Claim and Start Work

# Update issue to in_progress
tracer update <issue-id> --status in_progress --json

# Example:
tracer update bd-1 --status in_progress

3. Create Issues During Work

As you discover new work, file it immediately:

# Create a bug you found
tracer create "Fix edge case in validation" -t bug -p 0 --json

# Link it back to parent work with discovered-from
tracer dep add <new-issue-id> <parent-issue-id> --type discovered-from

4. Add Dependencies

When you realize work blocks other work:

# bd-2 is blocked by bd-1
tracer dep add bd-2 bd-1 --type blocks

# For parent-child relationships (epics)
tracer dep add bd-3 bd-1 --type parent-child

5. Complete Work

# Close the issue
tracer close <issue-id> --reason "Implemented and tested"

# Example with multiple issues
tracer close bd-1 bd-2 bd-3 --reason "All completed"

6. Check Status

# View issue details
tracer show <issue-id> --json

# See overall statistics
tracer stats --json

# Check what's blocked
tracer blocked --json

JSON Output Format

All commands support --json for programmatic parsing:

Ready Work Response

[
  {
    "id": "bd-1",
    "title": "Implement feature X",
    "status": "open",
    "priority": 1,
    "issue_type": "feature",
    "created_at": "2025-10-15T10:00:00Z",
    "updated_at": "2025-10-15T10:00:00Z"
  }
]

Read the full file on GitHub · 409 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. 2mo ago First seen · 409 lines · 2,428 tokens per session scan A f0f8a931aeb9

Subscribe to this mod's changes

tracer AGENTS.md is an instructions file published in the GitHub repository Abil-Shrestha/tracer (23 stars, last pushed 28d ago), licensed MIT. It adds 2,428 tokens to every session, about $0.0097 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.

Related

tracer AGENTS.md compared with instructions from other repositories

tracer AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
tracer AGENTS.mdAbil-Shrestha/tracerInstructions file2328d agoMITA2,428Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode