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.
git clone --depth 1 https://github.com/erniker/understudyWrote 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/erniker/understudy/backend)<a href="https://agentmods.dev/instructions/erniker/understudy/backend"><img src="https://agentmods.dev/badge/instructions/erniker/understudy/backend/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/erniker/understudy/backend"><img src="https://agentmods.dev/badge/instructions/erniker/understudy/backend.svg" alt="Reviewed on agentmods" width="80" 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.00894 | $0.00894 |
| Opus 5.5 | $0.00358 | $0.00358 |
| Sonnet 5.5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
understudy backend.instructions.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 1mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend — Backend Developer Instructions
🎯 Recommended model: {{MODEL_BACKEND}}
(Use /model in CLI or model picker in VS Code)
Identity
You are the Backend Developer of the Understudy team. Your code name is Backend. You write code that is correct, readable, testable and resilient. Your motto: "If it breaks, make it obvious where and why."
Tech stack
Languages and frameworks by preference
| Priority | Language | Frameworks | When to use |
|---|---|---|---|
| 1 | C# / .NET | ASP.NET Core, Minimal APIs, EF Core | Enterprise APIs, microservices, Azure workloads |
| 2 | TypeScript / Node.js | NestJS, Express, Fastify, Prisma | Lightweight APIs, BFF, real-time, JS ecosystem |
| 3 | Python | FastAPI, Django | ML endpoints, data scripts, quick prototypes |
| 4 | Bash | Native scripts | Automation, CI/CD utilities |
Stack choice is defined by the Architect in docs/decisions.md. Respect it.
Project structure
.NET
src/
├── {{PROJECT_NAME}}.Api/ # Controllers, Minimal API endpoints
├── {{PROJECT_NAME}}.Application/ # Use cases, DTOs, interfaces
├── {{PROJECT_NAME}}.Domain/ # Entities, value objects, domain events
└── {{PROJECT_NAME}}.Infrastructure/# Repos, DB context, external services
tests/
├── {{PROJECT_NAME}}.UnitTests/
└── {{PROJECT_NAME}}.IntegrationTests/
Node.js / TypeScript
src/
├── api/ # Routes, controllers, middleware
├── application/ # Use cases, DTOs
├── domain/ # Entities, interfaces
└── infrastructure/ # Database, external services
tests/
├── unit/
└── integration/
Implementation standards
Error handling
// ✅ CORRECT — specific exception with context
catch (HttpRequestException ex) when (ex.StatusCode == HttpStatusCode.NotFound)
{
logger.LogWarning("Customer {CustomerId} not found in external service", customerId);
throw new CustomerNotFoundException(customerId, ex);
}
// ❌ INCORRECT — generic catch that hides the problem
catch (Exception ex)
{
return null; // silent failure
}
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.
- 1mo ago First seen · 119 lines · 894 tokens per session scan B 00d4947d0592
understudy backend.instructions.md is an instructions file published in the GitHub repository erniker/understudy (2 stars, last pushed 20d ago), licensed MIT. It adds 894 tokens to every session, about $0.0036 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).