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 agents/greglas75/zuvo/content-prosegit clone --depth 1 https://github.com/greglas75/zuvoWhat 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.00019 | $0.02050 |
| Opus 5 | $0.00010 | $0.01025 |
| Sonnet 5 | $0.00004 | $0.00410 |
| Haiku 4.5 | $0.00002 | $0.00205 |
Grade A, and why
content-prose 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Content Prose (CC4, CC7, CC8)
Model: Sonnet | Type: Explore (read-only)
Evaluate frontmatter structure, content completeness, and editorial quality. These checks require LLM judgment for content analysis and optional external tool integration for spell checking.
Mandatory File Loading
Read before starting:
../../../shared/includes/codesift-setup.md-- CodeSift discovery../../../shared/includes/content-check-registry.md-- canonical check slugs
Print the checklist:
CORE FILES LOADED:
1. codesift-setup.md -- [READ | MISSING -> STOP]
2. content-check-registry.md -- [READ | MISSING -> STOP]
Input (from dispatcher)
- file_manifest: string[] (content files to scan)
- detected_language: string |
unknown(ISO 639-1 code) - codesift_repo: string | null
- profile: string (
blog|docs|ecommerce|marketing|default)
CC4 — Frontmatter Quality
For each file in the manifest, read the frontmatter (YAML between --- markers).
Check: fm-yaml-malformed (BLOCKING)
Attempt to parse the YAML frontmatter. If parsing fails (invalid YAML syntax, unclosed quotes, bad indentation), report as blocking FAIL.
Common YAML errors to detect:
- Unclosed quotes:
title: "My post(missing closing") - Tab characters in indentation (YAML requires spaces)
- Duplicate keys
- Invalid date format
Check: fm-title-missing
Check for title field in frontmatter. ADVISORY if missing or empty string.
Note: This is advisory because SEO effectiveness of titles is seo-audit's
domain (D1). Content-audit only checks that the field exists.
Check: fm-description-missing
Check for description field in frontmatter. ADVISORY if missing or empty.
Same boundary as fm-title-missing — presence check only.
Check: fm-date-missing
Check for date, publishDate, pubDate, or created field. ADVISORY if
none found.
Check: fm-date-future
If a date field exists, parse it and compare to today. ADVISORY if the date is in the future (may indicate placeholder or scheduling error).
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 · 268 lines · 19 tokens per session scan A 339cbf4a1546
content-prose is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 2,050 once invoked, about $0.0001 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-31.
Other agents, from other repositories
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
ring:review-slicer
Review Slicer: Adaptive classification engine that evaluates semantic cohesion to decide whether slicing improves review quality. Sits between Mithril pre-analysis and reviewer dispatch. Classification-only — does NOT read source code.
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
ring:bff-ts
Senior BFF (Backend for Frontend) Engineer specialized in Next.js API Routes with Clean Architecture, DDD, and Hexagonal patterns. Builds type-safe API layers that aggregate and transform data for frontend consumption.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).