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/sandeepshekhar26/develop-anything/claude-mdgit clone --depth 1 https://github.com/sandeepshekhar26/develop-anythingWrote 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/sandeepshekhar26/develop-anything/claude-md)<a href="https://agentmods.dev/instructions/sandeepshekhar26/develop-anything/claude-md"><img src="https://agentmods.dev/badge/instructions/sandeepshekhar26/develop-anything/claude-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.02399 | $0.02399 |
| Opus 5 | $0.01200 | $0.01200 |
| Sonnet 5 | $0.00480 | $0.00480 |
| Haiku 4.5 | $0.00240 | $0.00240 |
Grade A, and why
develop-anything 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 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.
This is a copy
98% identical to develop-anything AGENTS.md — 20 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generated by auk — AI Context Engineering Platform
https://github.com/sandeepshekhar26/develop-anything
Generated: 2026-06-11T17:08:30.051Z
Context Health: 100%
DO NOT EDIT MANUALLY — regenerate with: auk compile
Project: auk
Languages: typescript, javascript Framework: Express Rules: 24 | Health: 100%
📍 Project Overview
auk is a codebase (93 source files, primarily typescript/javascript).
Commands:
npm run dev # Dev (frontend)
npm run start # Start (frontend)
npm run build # Build (frontend)
npm run test # Test (frontend)
npm run typecheck # Typecheck (frontend)
Entrypoints:
dist/index.js— Package main entry (package.json "main")
Directory map:
src/commands/— source — 11 files, mostly typescriptsrc/analyzer/— source — 8 files, mostly typescriptsrc/compiler/targets/— source — 7 files, mostly typescriptsrc/utils/— shared utilities — 7 files, mostly typescriptsrc/generator/— source — 6 files, mostly typescriptsrc/reviewer/— source — 6 files, mostly typescriptsrc/decisions/— source — 5 files, mostly typescriptsrc/types/— type definitions — 5 files, mostly typescripttests/analyzer/— source — 5 files, mostly typescriptscripts/— build/dev scripts — 4 files, mostly javascriptsrc/semantic/— source — 4 files, mostly typescriptsrc/verifier/— source — 4 files, mostly typescript
⚠️ Critical Rules (ALWAYS follow these)
- architecture-no-utility-to-model: Utility layer should not import from Model layer. 1 existing violation is known tech debt — don't add more.
- naming-functions-camelcase: All function names use camelCase naming convention.
- naming-classes-pascalcase: All class and interface names use PascalCase naming convention.
- testing-naming-test: Test files follow the *.test.ts / *.test.js naming convention.
Architecture
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 · 260 lines · 2,399 tokens per session scan A 269426e874e5
develop-anything CLAUDE.md is an instructions file published in the GitHub repository sandeepshekhar26/develop-anything (17 stars, last pushed 2mo ago), licensed MIT. It adds 2,399 tokens to every session, about $0.0120 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to develop-anything AGENTS.md, differing in 20 lines, and is treated as a copy.
Other instructions, from other repositories
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.