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-encodinggit 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.00021 | $0.02303 |
| Opus 5 | $0.00010 | $0.01151 |
| Sonnet 5 | $0.00004 | $0.00461 |
| Haiku 4.5 | $0.00002 | $0.00230 |
Grade A, and why
content-encoding 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 yesterday.
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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Content Encoding (CC1, CC2, CC3)
Model: Sonnet | Type: Explore (read-only)
Scan content files for byte-level encoding issues, markdown formatting defects, and legacy CMS artifacts. All checks are grep/regex-based — no LLM judgment needed.
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]
If any file is missing, STOP.
Input (from dispatcher)
- file_manifest: string[] (content files to scan)
- detected_stack: string (
astro|nextjs|hugo|gatsby|generic) - codesift_repo: string | null
CC1 — Encoding Quality
Scan all files in the manifest for invisible Unicode characters and encoding corruption.
Check: nbsp-present
Search for non-breaking spaces (U+00A0):
Grep for the byte sequence \xC2\xA0 across content files
Alternative: search for the literal NBSP character. Report each occurrence with file:line.
Check: zero-width-present
Search for zero-width characters:
- U+200B (zero-width space)
- U+200C (zero-width non-joiner)
- U+200D (zero-width joiner)
- U+FEFF (BOM / zero-width no-break space, when not at file start)
Check: bom-present
Check first 3 bytes of each file for UTF-8 BOM marker (\xEF\xBB\xBF):
file -i <filepath> | grep -i bom
Or check first bytes: head -c 3 <file> | xxd | grep 'efbb bf'
Check: mojibake-detected (BLOCKING)
Search for garbled multi-byte sequences that indicate encoding corruption. This is the most critical check — mojibake means content is corrupted.
Grep patterns for common mojibake signatures:
Latin-1 / Windows-1252 corruption:
é|è|á|à |ó|ò|ü|ö|ä|ñ|ç|ê|î|â|ô|û|ï
ISO-8859-2 (Central European) corruption:
ą|ę|ś|ż|ź|ł|ń|ć|š|ž|ř|ů
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.
- yesterday First seen · 325 lines · 21 tokens per session scan A fff40e2954a5
content-encoding is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 2,303 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: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).
ring:prompt-reviewer
Expert Agent Quality Analyst evaluating AI agent executions against best practices, identifying prompt deficiencies, calculating quality scores, and generating precise improvement suggestions.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.