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/upgradegit 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.00000 | $0.00684 |
| Opus 5 | $0.00000 | $0.00342 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
upgrade 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade
Update EVC to the latest version, re-render templates with current config, and show what changed.
Trigger
User invokes /upgrade or says "update", "upgrade", "pull latest", "sync templates"
Steps
1. Pull latest changes
cd "{{PROJECT_ROOT}}"
git fetch origin
git log --oneline HEAD..origin/main | head -20
If there are new commits:
git pull origin main
If no new commits:
Already up to date. No changes to pull.
Show what changed:
git log --oneline --since="$(git log -1 --format=%ci HEAD@{1} 2>/dev/null || echo '1 week ago')" --until="now"
2. Re-render templates
Re-run setup.sh — it reads config.env and renders every _templates/ file with current tokens into .claude/commands/, .claude/hooks/, .claude/contexts/, and the brand/canon output paths. It is idempotent and will not overwrite config.env or brand/canon-rules.json.
./setup.sh
3. Show what changed
Compare rendered commands before and after:
# Diff the rendered output
git diff --stat .claude/commands/
Present a summary:
UPGRADE COMPLETE
════════════════════════════════════════
Source: [commit hash] -> [new commit hash]
New commits: [count]
TEMPLATES UPDATED
─────────────────
[list of changed command files]
NEW COMMANDS
─────────────────
[list of any new command files added]
REMOVED COMMANDS
─────────────────
[list of any command files removed]
CONFIG UNCHANGED
─────────────────
config.env and canon-rules.json were NOT modified.
(Templates never overwrite your local config.)
════════════════════════════════════════
4. Run validation
./scripts/validate.sh
Report any issues:
VALIDATION
─────────────────
Config: [PASS/FAIL]
Brand rules: [PASS/FAIL]
Templates: [PASS/FAIL]
Commands: [PASS/FAIL] ([count] commands)
[Any specific issues found]
5. Show changelog highlights
If a CHANGELOG.md exists in the repo root, show the latest entry:
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 · 123 lines · 0 tokens per session scan A 031141408c73
upgrade is a command published in the GitHub repository SaigonXIII/evc (56 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 684 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
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.
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.
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.