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/blog-qagit 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/blog-qa)<a href="https://agentmods.dev/commands/saigonxiii/evc/blog-qa"><img src="https://agentmods.dev/badge/commands/saigonxiii/evc/blog-qa.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.00000 | $0.01256 |
| Opus 5 | $0.00000 | $0.00628 |
| Sonnet 5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
blog-qa 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog QA
Run the full quality pipeline on a blog draft. Chains /content-qa + /stop-slop + blog-specific checks. Returns READY or NOT READY. Third step in the blog production pipeline.
Trigger
User invokes /blog-qa [slug] or says "QA the blog", "check the article", "is the blog ready"
Examples:
/blog-qa five-ways-to-write-a-better-headline/blog-qa product-launch-playbook
Prerequisites
- Draft must exist at
{{CONTENT_OUTPUT_DIR}}/blog/[slug]/copy.html - If no draft exists, prompt: "No draft found. Run
/blog-draft [slug]first."
Pipeline
Run all 8 checks in order. Each returns PASS, WARN, or FAIL.
Check 1: Canon Compliance
Load {{CONFIG_DIR}}/canon-rules.json. Scan the full copy against:
banned_phrases[]-- each match is FAILframing_red_flags[]-- each match is WARNusps[]-- claims not traceable to a USP are WARNrequired_language-- verify correct usagelive_partners[]vsdefunct_partners[]-- wrong partner reference is FAIL
Check 2: Stop Slop
Apply the stop-slop criteria — the canonical pattern list lives in /stop-slop (.claude/commands/stop-slop.md); do not maintain a separate list here.
Severity mapping for blog QA: filler phrases -> FAIL; all other stop-slop patterns -> WARN.
Check 3: Word Count + Structure
| Metric | Target | Check |
|---|---|---|
| Total words | 1,200-2,000 | FAIL if outside range |
| H2 sections | 5-7 | WARN if outside range |
| Avg paragraph length | 2-4 sentences | WARN if avg > 4 |
| Longest paragraph | Max 5 sentences | WARN if exceeded |
| H1 tags | 0 | FAIL if any present |
| Inline CSS | 0 | FAIL if any present |
Check 4: Canon Traceability
For every factual claim (numbers, percentages, partner names, fee amounts, product descriptions):
- Can it be traced to a specific canon document?
- If single-source only -> WARN ("unverified -- single source")
- If no source -> FAIL ("unsourced claim")
Check 5: Image Placeholders
- At least 2
<img class="blog-asset">tags present (cover + CTA minimum) -> FAIL if fewer - Every
<img>has descriptive alt text (not "image" or empty) -> WARN if missing - Image src paths follow
exports/[slug]-[name].pngpattern -> WARN if malformed
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 · 136 lines · 0 tokens per session scan A ae067c9b2904
blog-qa 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,256 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.
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.