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/fending/context-engineering/claude-mdgit clone --depth 1 https://github.com/fending/context-engineeringWhat 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.00003 | $0.00003 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
context-engineering 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.
This is a copy
100% identical to deepseek-harness CLAUDE.md — 0 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.
What it actually says
AGENTS.md
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 · 1 lines · 3 tokens per session scan A a54ff182c7e8
context-engineering CLAUDE.md is an instructions file published in the GitHub repository fending/context-engineering (11 stars, last pushed 5mo ago), licensed MIT. It adds 3 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to deepseek-harness CLAUDE.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
cocoindex-code CLAUDE.md
Instructions for cocoindex-io/cocoindex-code, covering claude.md, build and test commands, architecture, process model and key layers.
packmind AGENTS.md
Instructions for PackmindHub/packmind, covering core technologies, directory structure, local development environment, working with nx and code quality.
packmind CLAUDE.md
Instructions for PackmindHub/packmind, covering nx monorepo structure, core technologies, directory structure, local development environment and working with nx.
packmind packmind-backend-tests-redaction.instructions.md
Instructions for PackmindHub/packmind: This standard establishes best practices for writing backend tests using Jest in the Packmind monorepo. It focuses on clarity, maintainability, and consistency across test suites by emphasizing behavi... .
packmind packmind-frontend-data-flow.instructions.md
Instructions for PackmindHub/packmind: This standard defines the recommended data flow pattern for frontend routes in the Packmind codebase using React Router v7 in framework mode with TanStack Query for data management. It ensures consist... .
packmind packmind-nestjs-module-hierarchy.instructions.md
Instructions for PackmindHub/packmind: Establish a consistent NestJS module structure in the API application where each resource is encapsulated in its own module with proper hierarchical organization to enhance maintainability, scalabilit... .