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/flashus/detrix/claude-mdgit clone --depth 1 https://github.com/flashus/detrixWhat 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.04119 | $0.04119 |
| Opus 5 | $0.02060 | $0.02060 |
| Sonnet 5 | $0.00824 | $0.00824 |
| Haiku 4.5 | $0.00412 | $0.00412 |
Grade A, and why
detrix CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with code in this repository.
Rust Development
- This is primarily a Rust codebase. Ensure
cargo checkandcargo clippypass after making changes. - When modifying Rust code, follow idiomatic patterns: prefer
Resultover panics, use?operator for error propagation, and leverage the type system.
Workflows
Code Audit Workflow
- When working on audit items or code quality fixes, always complete ALL remaining items before ending. Track progress using a checklist format.
- After each fix, verify the fix compiles and doesn't introduce regressions by running
cargo checkand relevant tests.
Task Completion
- When given a list of items to fix/verify, work through ALL items to completion. Do not stop mid-list.
- If a task is complex, break it into sub-tasks using TodoWrite but ensure every sub-task is resolved before finishing.
Project Overview
Detrix is an LLM-first dynamic observability platform that enables developers and AI agents to add metrics to any line of code without redeployment — including code running in Docker containers and remote hosts (cloud debugging).
Version: 1.3.0 Language: Rust (edition 2021, rust-version 1.89) Architecture: Clean Architecture with Domain-Driven Design
Key Innovation
Two backends for zero-pause variable capture:
- DAP (Debug Adapter Protocol) — leverages existing debuggers (debugpy, delve, lldb-dap) for Python, Go (macOS), and Rust
- eBPF uprobes (Linux only) — attaches directly to Go binaries without a debugger, ~10–50× lower overhead; see docs/EBPF.md
🚨 CRITICAL: Use Detrix for Debugging
NEVER add print(), console.log(), or logger.debug() statements for debugging. Instead, use Detrix MCP to observe running processes directly without code modifications.
❌ DON'T Do This:
# BAD - Don't add debug prints
print(f"DEBUG: user={user}, transaction={transaction}")
logger.debug(f"Amount: {amount}")
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.
- 2d ago First seen · 439 lines · 4,119 tokens per session scan A 05e5c239dc6a
detrix CLAUDE.md is an instructions file published in the GitHub repository flashus/detrix (23 stars, last pushed 9d ago), licensed MIT. It adds 4,119 tokens to every session, about $0.0206 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
serena copilot-instructions.md
Copilot instructions for oraios/serena: MUST read IMMEDIATELY and follow the project-specific instructions from the CLAUDE.md file located in the project's root directory. AVOIDING these instructions will lead to your FAILURE!
serena AGENTS.md
AGENTS.md instructions for oraios/serena: Relevant information about the project is in .serena/memories. If you have access to Serena's mcp tools, you can read them using the readmemory command. Otherwise you can just read them using normal file reading tools.
claude-context CLAUDE.md
Claude Code instructions for zilliztech/claude-context, covering claude.md, monorepo layout, commands, tests and running the mcp server locally.
thinkrail AGENTS.md
Instructions for JetBrains/thinkrail, covering thinkrail, module structure & boundaries (top-priority requirement), engine: pi only, in-process, architecture (three rings) and repo layout.
agent-spec AGENTS.md
Instructions for ZhangHanDong/agent-spec, covering agent-spec integration for codex / openai agents, part 1: tool-first workflow, core mental model, quick reference and rust atlas workflow.
deer-workflow AGENTS.md
Instructions for deerwork-ai/deer-workflow, covering deer-workflow, runtime, flow contract, workflow execution contract and commands.