Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packnpx agentmods add commands/evan043/claude-cli-advanced-starter-pack/golden-master.templateWrote 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/commands/evan043/claude-cli-advanced-starter-pack/golden-master.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/golden-master.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/golden-master.template.svg" alt="Measured on agentmods" 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.00000 | $0.02750 |
| Opus 5 | $0.00000 | $0.01375 |
| Sonnet 5 | $0.00000 | $0.00550 |
| Haiku 4.5 | $0.00000 | $0.00275 |
Grade A, and why
golden-master.template 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 8d 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Generate characterization tests before refactoring (Golden Master pattern) model: sonnet argument-hint: [file path or function name]
/golden-master - Characterization Test Generator
Capture the current behavior of code as "Golden Master" tests before refactoring. Ensures refactoring preserves existing behavior.
"No characterization tests = No refactoring." - Legacy Code Survival Rule
Quick Start
/golden-master src/api/client.ts # Generate tests for entire file
/golden-master src/api/client.ts:fetchData # Generate tests for specific function
/golden-master --verify # Re-run and compare against master
/golden-master --update # Update golden master after intentional changes
What Is Golden Master Testing?
Golden Master (also called Characterization or Approval Testing) captures the actual behavior of code, not what you think it should do:
Before Refactoring:
┌─────────────────────────────────────────────────────────┐
│ Input Set → Legacy Code → Capture Output (Golden Master)│
└─────────────────────────────────────────────────────────┘
After Refactoring:
┌─────────────────────────────────────────────────────────┐
│ Input Set → Refactored Code → Compare Against Master │
│ ↓ │
│ ✅ Match = Safe to continue │
│ ❌ Diff = Investigate! │
└─────────────────────────────────────────────────────────┘
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.
- 8d ago First seen · 396 lines · 0 tokens per session scan A a64078f6a817
golden-master.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,750 tokens. 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-30.
Other commands, from other repositories
verify-loop
A command that repeatedly checks recent code changes and tries to fix failures, with a configurable retry limit. It can run code review, builds, tests, linting, and type checks according to the project language.
eval
Manage eval-driven development workflow (define, check, report, list).
tdd
A command for test-driven development, a method where you write a failing test first, then code to pass it, and finally improve the code.
web-checklist
A checklist command for testing a website after a Git merge. It records checklist items in a file so progress can be viewed and individual checks can be marked complete.
test-coverage
Analyze test coverage and generate missing tests to reach 80%+ coverage.
test-plan
Generate a test strategy document — test matrix, coverage goals, and test pyramid allocation for the current project.