claude-code-trace AGENTS.md

Project instructions for a desktop application built with a Vite web interface and a Tauri Rust backend, including commands for development, checking, formatting, and testing.

In plain words
What is it for?
Use them when changing source code, tests, or build configuration so the project is formatted, type-checked, linted, and tested before committing.
Why use it?
They give coding agents the project's required commands and the checks expected after each change.

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/delexw/claude-code-trace/agents-md
Clone the repo
git clone --depth 1 https://github.com/delexw/claude-code-trace

Made for: Codex, OpenCode.

Per session 978 This file is loaded in full into every session.
When invoked 978 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.00978 $0.00978
Opus 5 $0.00489 $0.00489
Sonnet 5 $0.00196 $0.00196
Haiku 4.5 $0.00098 $0.00098

Measured yesterday against content hash 60f1891274ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

claude-code-trace 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 yesterday.

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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

AGENTS.md · 81 lines

How it starts

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

CLAUDE.md

Commands

# Dev
npm run dev              # Vite dev server
npm run tauri dev        # Full Tauri app

# Lint
npx oxlint              # JS/TS lint
cargo clippy --manifest-path src-tauri/Cargo.toml  # Rust lint

# Format
npx oxfmt               # JS/TS format
cargo fmt --manifest-path src-tauri/Cargo.toml     # Rust format

# Test
npx vitest run           # Frontend tests
cargo test --manifest-path src-tauri/Cargo.toml    # Rust tests

# Type check
npx tsc --noEmit

# All at once
npm run check            # tsc + oxlint + oxfmt --check + clippy + cargo fmt --check + vitest + cargo test

Rule

After every code change (src, tests, config that affects build), always add enough tests for the changes, then run lint, format, and test before committing:

npx oxfmt && npx oxlint && npx tsc --noEmit && npx vitest run && cargo fmt --manifest-path src-tauri/Cargo.toml && cargo clippy --manifest-path src-tauri/Cargo.toml && cargo test --manifest-path src-tauri/Cargo.toml

GitNexus — Code Intelligence

This project is indexed by GitNexus as claude-code-trace (2596 symbols, 5375 relationships, 223 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.

If any GitNexus tool warns the index is stale, run npx gitnexus analyze in terminal first.

Always Do

  • MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run gitnexus_impact({target: "symbolName", direction: "upstream"}) and report the blast radius (direct callers, affected processes, risk level) to the user.
  • MUST run gitnexus_detect_changes() before committing to verify your changes only affect expected symbols and execution flows.
  • MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
  • When exploring unfamiliar code, use gitnexus_query({query: "concept"}) to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
  • When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use gitnexus_context({name: "symbolName"}).

Read the full file on GitHub · 81 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. yesterday First seen · 81 lines · 978 tokens per session scan A 60f1891274ed

Subscribe to this mod's changes

claude-code-trace AGENTS.md is an instructions file published in the GitHub repository delexw/claude-code-trace (348 stars, last pushed 2d ago), licensed MIT. It adds 978 tokens to every session, about $0.0049 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

codex-trace AGENTS.md

Instructions for PixelPaw-Labs/codex-trace, covering claude.md, commands, dev, lint and format.

PixelPaw-Labs/codex-trace · 611 tokens

codex-trace CLAUDE.md

Instructions for PixelPaw-Labs/codex-trace, a project described as: OpenAI Codex CLI session log viewer for JSONL files in /.codex/sessions. Browse conversations, tool calls, tokens, collaboration chains, and live sessions on desktop and web.

PixelPaw-Labs/codex-trace · 3 tokens

recharts AGENTS.md

Instructions for recharts/recharts: This is Recharts repository. Recharts is a React-based charting library. The goal is to provide a simple, declarative, and composable way to build charts. We value consistency, usability, and performance. Accessibility is important.

recharts/recharts · 310 tokens

payload AGENTS.md

Instructions for payloadcms/payload, a project described as: Payload is the open-source, fullstack Next.js framework, giving you instant backend superpowers. Get a full TypeScript backend and admin panel instantly. Use Payload as a headless CMS or for building powerful applications.

payloadcms/payload · 12 tokens

core CLAUDE.md

Claude Code instructions for module-federation/core, covering claude task parallelization & development guidelines, core principles, maximum parallelization strategy, universal parallel task patterns and for any codebase task.

module-federation/core · 3,933 tokens

ui-components AGENTS.md

Instructions for starc007/ui-components, covering beui v2 — agent guide, commands, layout, component catalog and components (motion category — primitives).

starc007/ui-components · 6,500 tokens