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 skills add rp1-run/rp1 --skill generate-user-docsgit clone --depth 1 https://github.com/rp1-run/rp1Wrote 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/rp1-run/rp1/generate-user-docs)<a href="https://agentmods.dev/skills/rp1-run/rp1/generate-user-docs"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/generate-user-docs.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.02670 |
| Opus 5 | $0.00015 | $0.01335 |
| Sonnet 5 | $0.00006 | $0.00534 |
| Haiku 4.5 | $0.00003 | $0.00267 |
Grade A, and why
generate-user-docs 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 8d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate User Docs
§ROLE: User-doc sync orchestrator. Reconcile user-facing docs against {kbRoot}/ in one scan pass and one process pass.
§OBJ
- Sync docs to current KB facts
- Keep orchestration state under
{workRoot}/ - Delegate file-level scan/process only
- Ask approval exactly once after scan
- If the KB is stale but structurally valid, require one explicit pre-scan decision gate
§DO
- Execute discovery + scan immediately
- Use
rp1-base:scribeonly for file batches - Spawn scan/process batches in parallel with background dispatch
- When the KB is stale, warn with a three-way gate: continue, rebuild first, or cancel
- Keep user-visible output terse:
- KB validation status
- Scan summary + approval gate
- Final report
- Preserve
scan_results.json; do NOT delete it automatically
§DONT
- Do NOT ask approval before scan
- Do NOT edit docs directly in the parent
- Do NOT iterate on scan or process more than once
- Do NOT silently continue with a stale KB
- Do NOT treat diffs inside the docs being reconciled as KB-staleness signals for this run
§PATHS
- Use the
RUN_IDfrom the generated Workflow Bootstrap section - Derive
RUN_NAMEas"Docs: sync user docs"(max 60 chars) - Set
DATESTAMPto the current date inYYYY-MM-DD - Set
SESSION_DIR=docs-sync/{DATESTAMP}-{RUN_ID} - Set
SCAN_RESULTS_REL={SESSION_DIR}/scan_results.json - Set
SCAN_RESULTS_PATH={workRoot}/{SCAN_RESULTS_REL}
References
| File | Purpose | When to Load |
|---|---|---|
references/kb-validation.md |
KB staleness gate, missing-file handling, format checks | When the validate step runs |
references/processing.md |
Per-doc update procedure, artifact registration, completion reporting | After approval returns an approved change set |
STATE-MACHINE
stateDiagram-v2
[*] --> discover
discover --> validate_kb : docs_ready
discover --> failed : no_docs
validate_kb --> scan : kb_current
validate_kb --> stale_kb_gate : kb_stale
validate_kb --> failed : kb_invalid
stale_kb_gate --> scan : continue_with_stale
stale_kb_gate --> cancelled : rebuild_requested
stale_kb_gate --> cancelled : rejected
scan --> approve : results_written
scan --> failed : scan_failed
approve --> process : approved
approve --> cancelled : rejected
process --> finalize : processing_done
process --> failed : process_failed
finalize --> [*] : done
failed --> [*] : stopped
cancelled --> [*] : stopped
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.
- 8d ago First seen · 357 lines · 29 tokens per session scan A 8e0ce3dd1285
generate-user-docs is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 2,670 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-30.
Other skills, from other repositories
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.
brainstorm
Explore ambiguous or early-stage ideas interactively — tracks wish-readiness and crystallizes into a design for wish.
refactor-advisor
A code review helper that finds common design and maintenance problems in a codebase and suggests ways to restructure the code.
acceptance-test-authoring
Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an acceptance stack, or implementing OpenSpec tasks that involve acceptance tests.