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/saigonxiii/evc/reference-capturegit clone --depth 1 https://github.com/SaigonXIII/evcWhat 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.00026 | $0.01199 |
| Opus 5 | $0.00013 | $0.00600 |
| Sonnet 5 | $0.00005 | $0.00240 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
reference-capture 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 2d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reference Capture
Screenshot what currently exists before building anything new. Every visual-build command (/blog-assets, /content, etc.) requires a recent reference capture — the check-reference hook will block the build if none exists.
Usage
/project:reference-capture [target]
/project:reference-capture https://acme.com/blog
/project:reference-capture homepage-hero
/project:reference-capture --intentional blog-redesign # mark as intentional divergence
Why
Most rework comes from assumptions about what's already there. Before designing a new blog cover, you need to see the current covers. Before redesigning a hero, you need to see the existing hero. This command forces that step.
Prerequisites
- Playwright MCP available (preferred) OR manual PNG drop supported
WEBSITE_URLset inconfig.env(unlessALLOW_GREENFIELD=true)
Steps
1. Parse target
- If target starts with
http://orhttps://→ use as URL directly - If target is a slug or name (e.g.
homepage-hero,blog) → resolve via config:homepage→https://{{WEBSITE_URL}}blog→https://{{WEBSITE_URL}}/blogblog-[slug]→https://{{WEBSITE_URL}}/blog/[slug]- Other names → prompt user for full URL
2. Capture screenshot
If Playwright MCP is available:
mcp__playwright__browser_navigate (url)
mcp__playwright__browser_resize (1200, 675)
mcp__playwright__browser_take_screenshot (fullPage: false, filename: [slug]-[date].png)
If Playwright unavailable: Print manual instructions:
Playwright MCP not available. Take a screenshot manually:
1. Open [url] in your browser
2. Capture at 1200×675
3. Save to: staging/references/[YYYY-MM-DD]-[slug].png
4. Re-run this command to register it in the log
3. Save to staging/references/
Path: staging/references/[YYYY-MM-DD]-[slug].png
Where [slug] is:
- Sanitized from the target name (lowercase, hyphens, no special chars)
- Or derived from URL path (e.g.
example.com/blog/headlines→blog-headlines)
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.
- 2d ago First seen · 135 lines · 26 tokens per session scan A fbc4cad1ccb1
reference-capture is a command published in the GitHub repository SaigonXIII/evc (56 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 1,199 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-30.
Other commands, from other repositories
review-tool
Research a tool or product for skill-gap, architecture, and verb-fit per the Anatomy framework.
setup
First-run setup — replace the fictional company and authors with yours.
content-status
Scan all content directories and report status of drafts, ideas, and published content.
draft-blog
Scaffold a blog post with proper structure, voice, and frontmatter.
review-content
Review content for brand alignment, lead placement, bio consistency, and proof points.
voice-check
Check a draft against the author's voice profile and flag deviations.