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/sitouhemi/backendgen/agents-mdgit clone --depth 1 https://github.com/SiTouhemi/BackendgenWrote 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/sitouhemi/backendgen/agents-md)<a href="https://agentmods.dev/instructions/sitouhemi/backendgen/agents-md"><img src="https://agentmods.dev/badge/instructions/sitouhemi/backendgen/agents-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.00359 | $0.00359 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
Backendgen AGENTS.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 3d 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.
What it actually says
Project: Backend Compiler
Mission
Build a deterministic backend feature compiler for coding agents. Agents submit a compact, versioned specification; the compiler validates it, creates a normalized intermediate representation, and eventually generates tested backend repositories.
Current scope
- TypeScript 5 and Node.js 22.
- npm workspaces.
- NestJS + Prisma + PostgreSQL is the first future target.
- FastAPI is explicitly out of scope until the first target and feature conformance tests are stable.
- The compiler must work locally without a SaaS account.
Commands
- Install:
npm install - Build:
npm run build - Test:
npm test - Validate example:
npm run validate:example - Inspect example IR:
npm run inspect:example
Architecture rules
- The versioned specification is the public contract.
- YAML/JSON input must never be passed directly to target templates.
- All generators consume the normalized
BackendIR. - Validation errors must include a stable code and a useful path.
- Agent-facing output should be concise and structured; never return generated file contents by default.
- Features own domain semantics; targets own framework-specific rendering.
- Generated and custom application code must remain separable.
Code conventions
- Use named exports.
- Keep modules focused and colocate tests with source.
- Prefer immutable data and pure compilation steps.
- Do not silently invent defaults that change security or data ownership.
- Add tests for every validation rule and IR transformation.
Boundaries
- Never commit secrets or generated customer projects.
- Do not add a second target before the first target passes conformance tests.
- Do not add SaaS infrastructure before local design-partner validation.
- Run build and tests before considering a change complete.
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.
- 3d ago First seen · 47 lines · 359 tokens per session scan A 7d3cffab461d
Backendgen AGENTS.md is an instructions file published in the GitHub repository SiTouhemi/Backendgen (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 359 tokens to every session, about $0.0018 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
react-seed AGENTS.md
Instructions for guokaigdg/react-seed, covering agents.md, 目录, 1. 项目概览, 2. 技术栈 and 3. 目录结构.
agentic-playwright enums.instructions.md
Instructions for idavidov13/agentic-playwright, covering enums, critical, file locations, instructions and phase 1: decide if the value belongs in an enum.
ui-extensions-sdk CLAUDE.md
Instructions for contentful/ui-extensions-sdk, covering claude project instructions — ui-extensions-sdk, identity & scope, working style, sharp edges and verification before claiming done.
hana-developer-cli-tool-example mcp-server-development.instructions.md
Use when creating or updating MCP (Model Context Protocol) server components. Enforces TypeScript patterns, JSON-RPC communication rules, tool/resource/prompt registration, and integration with CLI command metadata. Ensures MCP server follows protocol requirements and maintains consistency with the CLI infrastructure.
innovation-lab-examples typescript.instructions.md
Instructions for fetchai/innovation-lab-examples, a project described as: 80+ production-ready AI agent examples in Python — build autonomous agents, multi-agent systems and agentic AI with uAgents, ASI:One, MCP, A2A, LangChain, CrewAI, Gemini, Claude and OpenAI.
starknet-agentic CLAUDE.md
Instructions for keep-starknet-strange/starknet-agentic, covering starknet agentic -- development context, cairo, typescript, skills and git.