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.
npx agentmods add instructions/abil-shrestha/tracer/agents-mdgit clone --depth 1 https://github.com/Abil-Shrestha/tracerWrote 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/abil-shrestha/tracer/agents-md)<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="Measured on agentmods" 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 | $0.02428 | $0.02428 |
| Opus 5 | $0.01214 | $0.01214 |
| Sonnet 5 | $0.00486 | $0.00486 |
| Haiku 4.5 | $0.00243 | $0.00243 |
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 4d 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 — 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"
}
]
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.
- 4d ago First seen · 409 lines · 2,428 tokens per session scan A f0f8a931aeb9
tracer AGENTS.md is an instructions file published in the GitHub repository Abil-Shrestha/tracer (22 stars, last pushed 10mo ago), licensed MIT. It adds 2,428 tokens to every session, about $0.0121 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.
Other instructions, from other repositories
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
tmetric-minimal-mcp CLAUDE.md
Claude Code instructions for guglielmo/tmetric-minimal-mcp, covering claude.md, development commands, project architecture, file structure and core architecture patterns.
shelly-forge CLAUDE.md
Claude Code instructions for mslavov/shelly-forge, covering documentation usage guidelines, critical: framework-first reading order, 📚 mandatory reading order, pre-task protocol and post-task protocol.
vibelive AGENTS.md
AGENTS.md instructions for pooriaarab/vibelive, covering agents.md, repository context, pull requests, cloud agents (cursor) and install & test.
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).