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/site-auditgit clone --depth 1 https://github.com/SaigonXIII/evcWrote 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/site-audit)<a href="https://agentmods.dev/commands/saigonxiii/evc/site-audit"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/site-audit.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 | $0.00035 | $0.01117 |
| Opus 5 | $0.00017 | $0.00558 |
| Sonnet 5 | $0.00007 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
site-audit 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 5d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Audit
Scan the live {{WEBSITE_URL}} site for copy that conflicts with the brand canon. Returns a prioritised list of issues with the exact node IDs needed to fix them.
Usage
/site-audit
No arguments needed. Connects to the active site builder or CMS via MCP if one is available.
Prerequisites
- A site source: either a site-builder MCP plugin showing "online", a CMS with an accessible API, or a list of public URLs you can provide
brand/canon-rules.jsonmust exist and be populated (run/setup-canonfirst if not)
Steps
1. Load the brand canon
Read brand/canon-rules.json and hold in memory:
banned_phrases[]— with reasonsframing_red_flags[]defunct_partners[]— must never appear anywhere on the sitelive_partners[]— names the site SHOULD be consistent aboutrequired_language.product_name— spelling and casingrequired_language.company_anchor— the positioning statement that should appear on the homepage / herousps[]— the selling points the site should reinforceaudience+positioning— the frame the site should be written forcompliance_rules[<jurisdiction>]— ifCOMPLIANCE_JURISDICTIONSis set inconfig.env
If canon fields are empty, note the gap and continue with what's available. Do not audit against rules the user hasn't defined.
2. Collect site content
Source the text from whichever surface is available:
- Site-builder MCP (Framer, Webflow, Figma Sites, etc.): list all public pages and pull text nodes with their node IDs
- CMS API: query all published collections/items
- URL list: if no MCP or CMS is wired, ask the user for the list of public URLs to audit and fetch them via WebFetch
For each piece of text captured, record:
- Source ID (node ID, CMS item ID, or URL + selector)
- Text content
- Page/location it lives on
3. Run the audit
Apply the same checks as /content-review, at site scale.
Critical — automatic fails
- Banned phrases: any match against
banned_phrases[]is a critical fail - Defunct references: any appearance of a name in
defunct_partners[]is a critical fail (these should be zero) - Compliance violations: any
banned_claimsfor an active jurisdiction
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.
- 5d ago First seen · 130 lines · 35 tokens per session scan A 1c030416c1b4
site-audit is a command published in the GitHub repository SaigonXIII/evc (56 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,117 once invoked, about $0.0002 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.
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.
review-content
Review content for brand alignment, lead placement, bio consistency, and proof points.