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/selance/madeinalgeria/claude-mdgit clone --depth 1 https://github.com/selance/madeinalgeriaWrote 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/selance/madeinalgeria/claude-md)<a href="https://agentmods.dev/instructions/selance/madeinalgeria/claude-md"><img src="https://agentmods.dev/badge/instructions/selance/madeinalgeria/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.02274 | $0.02274 |
| Opus 5 | $0.01137 | $0.01137 |
| Sonnet 5 | $0.00455 | $0.00455 |
| Haiku 4.5 | $0.00227 | $0.00227 |
Grade A, and why
madeinalgeria 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.
How it starts
The opening of the file, as written. The whole thing — 92 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 (claude.ai/code) when working with code in this repository.
Before any frontend/UI work, read .claude/rules/design-system.md. Before finishing a task, follow .claude/rules/workflow.md.
Commands
pnpm install
pnpm typecheck # all workspaces (parallel)
pnpm lint # oxlint (oxc.rs), whole repo — config in .oxlintrc.json
pnpm test # all workspaces (serial — workers tests can't run concurrently)
pnpm --filter @mia/api test # one workspace
pnpm --filter @mia/module-billing exec vitest run src/foo.test.ts # one file
pnpm dev:api # public API, local miniflare :8787 — never --remote
pnpm dev:admin-api # admin API :8788
pnpm --filter @mia/app dev # user dashboard SPA (vite :5173)
pnpm --filter @mia/admin-web dev # admin dashboard SPA (vite)
pnpm --filter @mia/web dev # public site (astro :4321)
DB (from apps/api): pnpm db:migrate:local|staging|production, pnpm seed:local|staging. Seeding is CLI-only (tools/seed) — never add HTTP seeding endpoints. New schema → edit packages/db-core/src/schema/*, then pnpm --filter @mia/db-core db:generate.
Deploys: every app has deploy:staging / deploy:production (wrangler). pnpm deploy:all at the root does staging then production for every workspace. CI (.github/workflows) deploys everything to staging on push to main; production workflow is manual dispatch.
Architecture
pnpm monorepo, modular monolith on Cloudflare Workers. Everything is TypeScript, Hono on the backend, React 19 on the frontend, Drizzle on D1.
Apps (apps/*, each a Worker):
api— public API. Hono + all modules, queue consumer (email.send,campaign.dispatch), better-auth mounted on/v1/auth/*.admin-api— admin API. Same modules' admin routers, globalrequireAdminbefore everything.web— public/SEO site (Astro static-first on a Worker). Middleware does not run for prerendered pages.app— user dashboard SPA. React Router (data mode), TanStack Query/Table, react-hook-form + zod.admin-web— admin dashboard SPA. Same stack asapp.
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 · 92 lines · 2,274 tokens per session scan A 14f2759e5658
madeinalgeria CLAUDE.md is an instructions file published in the GitHub repository selance/madeinalgeria (60 stars, last pushed 15d ago), licensed MIT. It adds 2,274 tokens to every session, about $0.0114 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
openscreen AGENTS.md
AGENTS.md instructions for getopenscreen/openscreen, covering agents.md, setup commands, development principles, project layout and code style.
Claw3D AGENTS.md
Instructions for iamlukethedev/Claw3D, covering agent instructions, cursor cloud specific instructions, service overview, running the app and lint, typecheck, and tests.
commonly CLAUDE.md
Claude Code instructions for Team-Commonly/commonly, covering claude.md / agents.md, 🧠 product vision & architecture philosophy, what commonly is, the architecture model and key concepts.
claude-ads CLAUDE.md
Instructions for AgriciDaniel/claude-ads, covering claude ads repository instructions, architecture, development and verification.
openstatus AGENTS.md
AGENTS.md instructions for openstatusHQ/openstatus, covering agents.md, verify your change, toolchain, architecture and tests.
windmill AGENTS.md
AGENTS.md instructions for windmill-labs/windmill, covering windmill, workflow, documentation, dev environment and per-worktree ports and database.