Borrowing it
Nothing to install: this file belongs to manfromtunis/claude-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/manfromtunis/claude-config/main/CLAUDE.mdgit clone --depth 1 https://github.com/manfromtunis/claude-configWrote 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/manfromtunis/claude-config/claude-md)<a href="https://agentmods.dev/instructions/manfromtunis/claude-config/claude-md"><img src="https://agentmods.dev/badge/instructions/manfromtunis/claude-config/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.1 | $0.01467 | $0.01467 |
| Opus 5 | $0.00733 | $0.00733 |
| Sonnet 5 | $0.00293 | $0.00293 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
claude-config 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 7d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Partnership Guide
Development Partnership Principles
We are partners in creating production-quality code. Every line of code we write together should be:
- Maintainable by the next developer
- Thoroughly tested and documented
- Designed to catch issues early rather than hide them
🚨 MANDATORY AI WORKFLOW
BEFORE DOING ANYTHING, YOU MUST:
ALWAYS use zen gemini for complex problems and architectural decisions
ALWAYS check Context7 for library documentation and best practices
SAY THIS PHRASE: "Let me research the codebase using zen gemini and Context7 to create a plan before implementing."
Critical Workflow
Research → Plan → Implement
NEVER jump straight to coding. Always follow this sequence:
- Research: Use multiple agents to understand the codebase, existing patterns, and requirements
- Plan: Create a detailed implementation plan with TodoWrite
- Implement: Execute the plan with continuous validation
Use Multiple Agents for Parallel Problem-Solving
When facing complex problems, launch multiple agents concurrently to:
- Research different aspects of the codebase
- Investigate various implementation approaches
- Validate assumptions and requirements
Mandatory Automated Checks and Reality Checkpoints
Before any code is considered complete:
- Run all linters and formatters
- Execute all tests
- Validate the feature works end-to-end
- Clean up any old/unused code
TypeScript/Next.js Specific Rules
Forbidden Practices
- NO any or unknown types: Always use specific types
- NO console.log in production: Use proper logging
- NO inline styles: Use Tailwind classes or CSS modules
- NO direct DOM manipulation: Use React patterns
Implementation Standards
Code is complete when:
- TypeScript compiler passes with strict mode
- ESLint passes with zero warnings
- All tests pass
- Next.js builds successfully
- Feature works end-to-end
- Old code is deleted
- JSDoc comments on all exported functions
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.
- 7d ago First seen · 259 lines · 1,467 tokens per session scan A 63581f44dc71
claude-config CLAUDE.md is an instructions file published in the GitHub repository manfromtunis/claude-config (2 stars, last pushed 7mo ago), licensed MIT. It adds 1,467 tokens to every session, about $0.0073 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-31.
Other instructions, from other repositories
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.