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/compliance-checkgit 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/compliance-check)<a href="https://agentmods.dev/commands/saigonxiii/evc/compliance-check"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/compliance-check.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.01803 |
| Opus 5 | $0.00000 | $0.00901 |
| Sonnet 5 | $0.00000 | $0.00361 |
| Haiku 4.5 | $0.00000 | $0.00180 |
Grade A, and why
compliance-check 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Check
Jurisdiction-aware content compliance validation. Scans copy for regulatory violations, banned claims, missing disclaimers, and financial promotion language.
Trigger
User invokes /compliance-check [file-or-text] or says "check compliance", "legal review", "is this compliant", "regulatory check"
Arguments
- Required: file path or inline text to check
- Optional:
--jurisdiction <US|EU|UK|ALL>(default: ALL) - Optional:
--type <social|blog|email|landing-page|influencer>(default: auto-detect)
Steps
1. Load compliance rules
Read rules from {{BRAND_DIR}}/canon-rules.json -> compliance_rules:
cat "{{BRAND_DIR}}/canon-rules.json" | jq '.compliance_rules'
If no compliance rules exist, use built-in defaults based on industry:
Web3 Defaults (pre-filled for crypto/blockchain):
{
"industry": "web3",
"banned_claims": [
"guaranteed returns",
"risk-free",
"no risk",
"can't lose",
"get rich",
"passive income guaranteed",
"100% safe",
"investment opportunity",
"financial advice"
],
"required_disclaimers": {
"token_mention": "This is not financial advice. Do your own research.",
"rewards_mention": "Rewards are subject to terms and conditions.",
"yield_mention": "Past performance is not indicative of future results."
},
"jurisdiction_rules": {
"US": {
"banned_words": ["security", "invest", "profit", "dividend", "yield"],
"context_note": "SEC scrutiny — avoid anything that implies token = security",
"required_if_financial": "Not available to US residents where prohibited."
},
"EU": {
"banned_words": ["guaranteed", "no-risk"],
"context_note": "MiCA regulation — clear risk disclosure required",
"required_if_financial": "Capital at risk. Please read the full terms."
},
"UK": {
"banned_words": ["guaranteed returns", "risk-free investment"],
"context_note": "FCA crypto marketing rules — must be fair, clear, not misleading",
"required_if_financial": "Don't invest unless you're prepared to lose all the money you invest."
}
}
}
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 · 241 lines · 0 tokens per session scan A 305d6d523fd4
compliance-check 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 1,803 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.
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.