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/delexw/claude-code-misc/claude-mdgit clone --depth 1 https://github.com/delexw/claude-code-miscWhat 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.01420 | $0.01420 |
| Opus 5 | $0.00710 | $0.00710 |
| Sonnet 5 | $0.00284 | $0.00284 |
| Haiku 4.5 | $0.00142 | $0.00142 |
Grade A, and why
claude-code-misc 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 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.
This is a copy
80% identical to claude-code-trace AGENTS.md — 125 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitNexus — Code Intelligence
This project is indexed by GitNexus as claude-code-misc (2969 symbols, 5641 relationships, 243 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 analyzein 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"}).
When Debugging
gitnexus_query({query: "<error or symptom>"})— find execution flows related to the issuegitnexus_context({name: "<suspect function>"})— see all callers, callees, and process participationREAD gitnexus://repo/claude-code-misc/process/{processName}— trace the full execution flow step by step- For regressions:
gitnexus_detect_changes({scope: "compare", base_ref: "main"})— see what your branch changed
When Refactoring
- Renaming: MUST use
gitnexus_rename({symbol_name: "old", new_name: "new", dry_run: true})first. Review the preview — graph edits are safe, text_search edits need manual review. Then run withdry_run: false. - Extracting/Splitting: MUST run
gitnexus_context({name: "target"})to see all incoming/outgoing refs, thengitnexus_impact({target: "target", direction: "upstream"})to find all external callers before moving code. - After any refactor: run
gitnexus_detect_changes({scope: "all"})to verify only expected files changed.
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.
- yesterday First seen · 102 lines · 1,420 tokens per session scan A dff49c7d0ed8
claude-code-misc CLAUDE.md is an instructions file published in the GitHub repository delexw/claude-code-misc (1 stars, last pushed 5mo ago), licensed MIT. It adds 1,420 tokens to every session, about $0.0071 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to claude-code-trace AGENTS.md, differing in 125 lines, and is treated as a copy.
Other instructions, from other repositories
webflow-skills CLAUDE.md
Instructions for webflow/webflow-skills, covering project overview, repository structure, ci validation, what ci checks and 2. marketplace and plugin configs exist.
rolecraft AGENTS.md
Instructions for rolecraft-sh/rolecraft, covering rolecraft — development guidelines, ⚠️ startup checklist (read before every task), workflow, interaction rules and code style.
MathModelAgent CLAUDE.md
Claude Code instructions for jihe520/MathModelAgent, covering claude.md, 项目概述, commands, 后端 and 安装依赖.
lime AGENTS.md
AGENTS.md instructions for limecloud/lime, covering lime 源码仓库指南, 事实源, 工程约束, 协议与质量 and 执行方式.
clean-code-skills clean-code.instructions.md
Instructions for btseee/clean-code-skills, covering clean-code instructions, clean code rules (clean-code-skills), work loop, dependency direction and file and code placement.
wtcraft CLAUDE.md
Instructions for zywkloo/wtcraft, covering wtcraft routing, repo structure (wtcraft dogfooding), model knowledge policy and release guardrails.