Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/greglas75/zuvonpx agentmods add skills/greglas75/zuvo/docsWrote 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/docs)<a href="https://agentmods.dev/skills/greglas75/zuvo/docs"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/greglas75/zuvo/docs"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/docs.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.04027 |
| Opus 5.5 | $0.00027 | $0.01611 |
| Sonnet 5.5 | $0.00014 | $0.00805 |
| Haiku 4.5 | $0.00007 | $0.00403 |
Grade C, and why
docs scanned grade C with 1 finding 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 10d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Evidence Map | Section | Source file(s) | |---------|---------------| | Quick Start | package.json:scripts (line 5-12) | | Configuration | .env.example (line 1-15) | | API: GET /users | src/routes/users.controller.t How it starts
The opening of the file, as written. The whole thing — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:docs — Technical Documentation
Generate or update documentation by reading the actual codebase -- not from templates, not from memory, from real code.
Iron rule: Never write a claim in documentation without reading the source file it references first. Every section maps back to a source file via the Evidence Map.
Scope: README, API reference, runbooks, onboarding guides, changelogs.
Out of scope: Architecture diagrams (use zuvo:architecture), code comments (out of scope), user-facing product docs (out of scope).
Argument Parsing
| Input | Action |
|---|---|
| (empty) | Check if README.md exists. If yes: update it. If no: generate one. If user interaction is available, ask for preference. |
readme [path] |
Write or update README for the module at [path] |
api [path] |
Generate API reference from route/controller files at [path] |
runbook [topic] |
Write operational runbook for a specific process |
onboarding |
Write onboarding guide for new developers |
update [file] |
Read existing doc, verify claims against source, patch stale sections |
changelog |
Generate CHANGELOG.md from git history |
changelog [range] |
Generate changelog for a specific range (e.g., v1.2.0..v1.3.0) |
Non-interactive environments (Codex, Cursor):
- No arguments: default to
readmefor project root - Target file exists: default to
updatemode (patch, not overwrite)
Mandatory File Loading
PHASE 0 — Bootstrap (before reading any source)
1. ../../shared/includes/codesift-setup.md -- [READ | MISSING -> WARN]
2. ../../shared/includes/env-compat.md -- [READ | MISSING -> WARN]
retrospective.md and run-logger.md are END-of-run includes — they are loaded at completion, not here.
Environment Compatibility
Read ../../shared/includes/env-compat.md for user interaction patterns.
CodeSift Integration
Read ../../shared/includes/codesift-setup.md for initialization.
Key tools for this skill:
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.
- 10d ago Changed · +2 lines 2a5290e44719
- 1mo ago Changed · -2 lines 99437908c799
- 1mo ago First seen · 459 lines · 68 tokens per session scan C 11b65869b8db
docs is a skill published in the GitHub repository greglas75/zuvo (8 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 4,027 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
changelog
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
wrap-up-branch
Finish a feature branch: add missing tests, review and fix the code, align docs, then merge only after explicit confirmation.
resolve-merge
Resolve an active merge or rebase conflict, including safe renumbering of colliding plans and chronicles.
commit
Create a user-requested Conventional Commit from the staged changes.
kanso-pr
Use when the user asks to write a pull request description, open a PR, draft PR notes, or summarise a branch for review.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…