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 commands/erniker/understudy/localize-projectgit clone --depth 1 https://github.com/erniker/understudyWhat 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.00028 | $0.00285 |
| Opus 5 | $0.00014 | $0.00143 |
| Sonnet 5 | $0.00006 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
localize-project 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 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.
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
The user wants this repository to have persistent, spec-driven memory instead of relying only on the machine-wide global team's session-by-session context.
Run the following from the repository root and report what it created:
understudy --docs-only --yes
This creates docs/spec.md, docs/decisions.md, docs/session-log.md,
docs/team-roster.md and a project-level understudy.yaml — real spec/ADR/
session-log tracking for this specific repo. It does not deploy or
duplicate any agent files: the team (Architect, Backend, Frontend, DevOps,
Security, QA, etc.) keeps coming from the global install.
If the user instead wants full per-project customization (different models
per role, apply_to scoping tailored to this repo's stack, project-specific
instructions instead of the shared global ones), tell them to run
understudy --here instead — it deploys the full per-project agent set on
top of whatever is already here, never removing anything.
If the understudy command is not on PATH, tell the user how to install it
(the one-liner in the project README) instead of failing silently.
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.
- yesterday First seen · 28 lines · 28 tokens per session scan A 366bb4ac789e
localize-project is a command published in the GitHub repository erniker/understudy (3 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 285 once invoked, about $0.0001 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 commands, from other repositories
oss-docs
(user-owned) oss-docs harness — README 4-locale + docs-site publishing for the moai-adk-go OSS project (adk.mo.ai.kr, Vercel auto-deploy).
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
plan
执行实施规划工作流，并使用计划模板生成设计制品。.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
graph
Execute a task through a cached, validated dependency graph with localized retries and a live report.
aso-audit
Audit App Store listing for keyword coverage, metadata limits, and conversion levers.