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 skills/greglas75/zuvo/content-expandnpx skills add greglas75/zuvo --skill content-expandgit clone --depth 1 https://github.com/greglas75/zuvoWrote 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/skills/greglas75/zuvo/content-expand)<a href="https://agentmods.dev/skills/greglas75/zuvo/content-expand"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/content-expand.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.00100 | $0.03834 |
| Opus 5 | $0.00050 | $0.01917 |
| Sonnet 5 | $0.00020 | $0.00767 |
| Haiku 4.5 | $0.00010 | $0.00383 |
Grade A, and why
content-expand 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 4d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:content-expand — Expand & Optimize Articles
Take an existing article, research the topic, add what's missing, and optimize the result — all in one pass. Same quality standards as zuvo:write-article.
Scope: Expand thin content, add missing sections, research and integrate new facts, optimize prose quality, update SEO/schema.
Out of scope: Encoding/markdown fixes (zuvo:content-audit + content-fix), writing from scratch (zuvo:write-article), CMS API, PDF/Word.
Mandatory File Loading
Phase 0 (always):
../../shared/includes/env-compat.md-- Agent dispatch../../shared/includes/run-logger.md-- Run logging../../shared/includes/banned-vocabulary/core.md-- Shared anti-slop rules, tone matrix, G12, fallback behavior../../shared/includes/humanization-rules.md-- Writing constraints + voice matching../../shared/includes/domain-profile-registry.md-- 17 niche profiles../../shared/includes/seo-page-profile-registry.md-- SEO profiles../../shared/includes/no-pause-protocol.md-- HARD: no mid-loop pauses (batch/multi-section)
Lazy-loaded (Phase 2 only):
../../shared/includes/prose-quality-registry.md-- PQ1-PQ18 (scoring)../../shared/includes/adversarial-loop-docs.md-- Cross-model review (end of Phase 2)../../shared/includes/article-output-schema.md-- JSON output../../shared/includes/retrospective.md-- RETRO PROTOCOL
Print CORE FILES LOADED: for items 1-7. After language detection, print LANGUAGE FILE: with the resolved banned-vocabulary language file and whether English fallback was used. Lazy items loaded inline when needed.
Safety Gates
GATE 1 — File Type
.md, .mdx supported. .html tolerated (tag-stripped, WARNING). Binary → STOP.
GATE 2 — Dirty File Check
git status --porcelain -- <file>. Uncommitted changes → STOP. Require commit or stash.
--dry-run mode: proceed with WARNING (no file mutation).
GATE 3 — Write Scope
Allowed: input file, <file>.content-expand-backup, zuvo/reports/. FORBIDDEN: everything else.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 283 lines · 100 tokens per session scan A e092c545a1f7
content-expand is a skill published in the GitHub repository greglas75/zuvo (6 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 3,834 once invoked, about $0.0005 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 skills, from other repositories
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
init
Write or refresh the ## Tech debt operations section in CLAUDE.md so a team shares one source of truth for debt-ops disciplines and cached quality commands. Idempotent. Only the managed section changes; other sections are untouched. Invoked explicitly via /debt-ops:init (solo users get the same content from the…
add
Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer…
metrics
Print a debt-ops health summary from the metrics log, covering registration rate, hook feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or invokes /debt-ops:metrics. Read-only, never writes the log.
review
Audit the debt registry, rank survivors by churn × Fowler quadrant, surface a top-N list, then walk paydown on user follow-up. Use when the user asks to review debt, see what to pay down, work through entries, or invokes /debt-ops:review. Stale entries drop with drop A,B,C.
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…