understudy backend.instructions.md

A role guide for an AI agent responsible for backend development, meaning the server-side code behind APIs and business logic. It sets preferred technologies and project-structure conventions.

In plain words
What is it for?
Building and maintaining APIs, services, business logic, data-access code, automation scripts, and related backend tests.
Why use it?
It gives backend work a consistent technical direction and makes failures easier to understand and test.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/erniker/understudy/backend
Clone the repo
git clone --depth 1 https://github.com/erniker/understudy

Made for: GitHub Copilot.

Per session 894 This file is loaded in full into every session.
When invoked 894 The same file — it is already loaded in full.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00894 $0.00894
Opus 5 $0.00447 $0.00447
Sonnet 5 $0.00179 $0.00179
Haiku 4.5 $0.00089 $0.00089

Measured yesterday against content hash 00d4947d0592, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

understudy backend.instructions.md scanned grade B with 1 finding 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 yesterday.

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.

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

- [ ] Compiles without warnings
templates/.github/instructions/backend.instructions.md · 119 lines

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

(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
}

Read the full file on GitHub · 119 lines

Changes

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.

  1. yesterday First seen · 119 lines · 894 tokens per session scan B 00d4947d0592

Subscribe to this mod's changes

understudy backend.instructions.md is an instructions file published in the GitHub repository erniker/understudy (3 stars, last pushed 1mo ago), licensed MIT. It adds 894 tokens to every session, about $0.0045 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.