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/agents/erniker/understudy/backend)<a href="https://agentmods.dev/agents/erniker/understudy/backend"><img src="https://agentmods.dev/badge/agents/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/agents/erniker/understudy/backend"><img src="https://agentmods.dev/badge/agents/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.00011 | $0.00906 |
| Opus 5.5 | $0.00004 | $0.00362 |
| Sonnet 5.5 | $0.00002 | $0.00181 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade B, and why
backend 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 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- [ ] Compiles without warnings How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend — Backend Developer
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, rapid prototypes |
| 4 | Bash | Native scripts | Automation, CI/CD utilities |
The 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
}
Logging
// ✅ CORRECT — structured log with context
logger.LogInformation(
"Processing payment {PaymentId} for customer {CustomerId}, amount {Amount}",
paymentId, customerId, amount);
// ❌ INCORRECT — string concatenation, no context
logger.LogInformation("Processing payment " + id);
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 · 124 lines · 11 tokens per session scan B da7b59d2034e
backend is an agent published in the GitHub repository erniker/understudy (2 stars, last pushed 20d ago), licensed MIT. It adds 11 tokens to every session and 906 once invoked, about $0.0000 per session on Opus 5.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.
Other agents, from other repositories
c4-container
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting…
api-scaffolding-backend-architect
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and…
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
temporal-python-pro
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.
api-testing-observability-api-documenter
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
business-analyst
Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.