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/yuri-semenenko/ai-engineering-workspace/backendgit clone --depth 1 https://github.com/yuri-semenenko/ai-engineering-workspaceWrote 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/yuri-semenenko/ai-engineering-workspace/backend)<a href="https://agentmods.dev/instructions/yuri-semenenko/ai-engineering-workspace/backend"><img src="https://agentmods.dev/badge/instructions/yuri-semenenko/ai-engineering-workspace/backend.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.00154 | $0.00154 |
| Opus 5 | $0.00077 | $0.00077 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
Backend Standards 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.
What it actually says
Backend Standards
Follow existing API and persistence patterns.
Prefer:
- explicit input validation
- narrow database queries
- clear transaction boundaries
- typed API contracts
- idempotent mutations where retries are possible
- structured error handling
- observable failure paths
Avoid:
- leaking internal errors to clients
- swallowing errors without context
- adding retries around logic bugs
- broad data fetches that create avoidable N+1 behavior
- schema changes without migration and rollback consideration
For SQL, prefer readable queries, explicit indexes for new access paths, and constraints that encode real invariants.
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 · 31 lines · 154 tokens per session scan A 09ad2482e4eb
Backend Standards is an instructions file published in the GitHub repository yuri-semenenko/ai-engineering-workspace (1 stars, last pushed 6d ago), licensed MIT. It adds 154 tokens to every session, about $0.0008 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
copilot-setting sql-ddl.instructions.md
Load when writing or reviewing MySQL DDL or migration scripts — CREATE/ALTER TABLE, indexes, stored procedures, backfills. Triggers on: ALTER TABLE, ALGORITHM=INSTANT/INPLACE, online schema change (pt-osc, gh-ost), rollback scripts, chunked backfill, DROP COLUMN, sp stored procedures. MySQL 8.0 / InnoDB. Query and…
copilot-setting sql.instructions.md
Load when writing or reviewing SQL in Java code — JDBC DAOs, HQL, query tuning. Triggers on: PreparedStatement/? (no concat), :paramName, no SELECT , WHERE on UPDATE/DELETE, indexes, EXPLAIN. Raw JDBC, not Spring Boot. DDL/migrations: sql-ddl.instructions.md. Defer Hibernate queries to spring-hibernate.instructions.md.
telegram-ai-bridge code-review.instructions.md
Instructions for legate-dev/telegram-ai-bridge, covering code review instructions, review posture, priority checklist, 1. contract compliance and 2. state integrity.
apex-accelerator vendor-prompting.instructions.md
Vendor prompting best-practice rules for Anthropic Claude and OpenAI GPT-5.6-Terra agents and prompts. Each rule cites a rule ID in the vendor-prompting skill rules.json registry. Validator: npm run lint:vendor-prompting.
vespertide AGENTS.md
AGENTS.md instructions for dev-five-git/vespertide, covering vespertide knowledge base, structure, where to look, data flow and conventions.
seekstone CLAUDE.md
Instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.