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/SaigonXIII/evcnpx agentmods add commands/saigonxiii/evc/upgradeWrote 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/saigonxiii/evc/upgrade)<a href="https://agentmods.dev/commands/saigonxiii/evc/upgrade"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/upgrade/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/commands/saigonxiii/evc/upgrade"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/upgrade.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.00000 | $0.00684 |
| Opus 5.5 | $0.00000 | $0.00274 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 123 lines · 0 tokens per session scan A 031141408c73
upgrade is a command published in the GitHub repository SaigonXIII/evc (59 stars, last pushed 4mo 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
release
Agent-native marketing CLI: 76 skills, 6 research/review agents, brand memory that compounds across sessions, and a local Studio dashboard. One npm install, then /cmo in your coding agent.
land
Resolve and squash merge one named, currently authorized pull request.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.