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/rules/erniker/understudy/understudy-global)<a href="https://agentmods.dev/rules/erniker/understudy/understudy-global"><img src="https://agentmods.dev/badge/rules/erniker/understudy/understudy-global/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/rules/erniker/understudy/understudy-global"><img src="https://agentmods.dev/badge/rules/erniker/understudy/understudy-global.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.00720 | $0.00720 |
| Opus 5.5 | $0.00288 | $0.00288 |
| Sonnet 5.5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade C, and why
understudy-global scanned grade C 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
Don't interrupt in-progress work to suggest this, and never refuse to keep How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{PROJECT_NAME}} — Project Instructions
Project
- Name: {{PROJECT_NAME}}
- Description: {{PROJECT_DESCRIPTION}}
- Main stack: {{TECH_STACK}}
- Repository: {{REPOSITORY_URL}}
- Project Manager: {{TEAM_LEAD}}
Team context
This project uses the Understudy system: a team of specialized AI agents.
Each agent has a defined role in .cursor/agents/ with detailed instructions.
Available roles are:
- architect — Solution design and architectural decisions
- backend — Implementation of APIs, services and business logic
- frontend — User interfaces and experience
- devops — Infrastructure, CI/CD and operations
- security — Security integrated throughout the entire cycle
- qa-engineer — Testing and software quality
To activate an agent, invoke it from the Agent panel in Cursor.
Spec-Driven Development
This project follows Spec-Driven Development:
- Before writing code, the specification is documented in
docs/spec.md - The spec must be approved by the PM before starting
- Any scope changes are reflected first in the spec
Mandatory context files
| File | Purpose |
|---|---|
docs/spec.md |
Project specification — the source of truth |
docs/decisions.md |
Architectural decision records (ADR) |
docs/session-log.md |
Session log — read at the start of each session |
docs/team-roster.md |
Active team roster and capabilities |
Global rules
At the start of a session
- Always read
docs/session-log.mdto know what was done before - Always read
docs/spec.mdfor project context - Always read
docs/decisions.mdfor decisions already made - Before working, confirm your understanding of the current state
At the end of a session
- Update
docs/session-log.mdwith:- What was done in this session
- What is still pending
- Decisions made
- Blockers identified
Recognizing good stopping points
A long conversation costs more (tokens, time, money) than starting fresh
with a concise summary. Watch for natural stopping points — a feature just
finished with tests passing, a bug fixed and verified, a question fully
answered — and proactively suggest wrapping up: update
docs/session-log.md, then tell the user this is a good point to close
this chat and start a new one, since the next session picks up full context
from docs/session-log.md — nothing is lost.
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 · 89 lines · 720 tokens per session scan C c95ff44a7f92
understudy-global is a cursor rule published in the GitHub repository erniker/understudy (2 stars, last pushed 20d ago), licensed MIT. It adds 720 tokens to every session, about $0.0029 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
nauro-context
Writes durable shared context into Nauro's project store so other agents (a later session or a parallel one) can discover and pull it, finds and reads context another agent left, or captures a resumable brief so your own next session in this environment picks up cleanly. Three modes. Author writes a shared brief for…
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
upload-report
Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types…
execute-test
Execute Katalon True Platform/TestOps tests when the input is an existing test case, manual test case list, test suite, suite collection, execution request, or "run with AI" instruction. Use when you need to create a manual test run, start Run with AI, poll AI session results, schedule automated suites, read…
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…