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 ruali-dev/Riven-Analyst --skill riven-knowledge-maintainergit clone --depth 1 https://github.com/ruali-dev/Riven-AnalystWrote 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/ruali-dev/riven-analyst/riven-knowledge-maintainer)<a href="https://agentmods.dev/skills/ruali-dev/riven-analyst/riven-knowledge-maintainer"><img src="https://agentmods.dev/badge/skills/ruali-dev/riven-analyst/riven-knowledge-maintainer.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.1 | $0.00048 | $0.00769 |
| Opus 5 | $0.00024 | $0.00385 |
| Sonnet 5 | $0.00010 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
riven-knowledge-maintainer 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 7d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Riven Knowledge Maintainer
Maintain the reviewed corpus through a human approval gate. Ordinary Riven analysis uses
riven-analyst; this Skill is only for proposing or applying an explicitly approved
knowledge change.
Non-negotiable write gate
The first turn for every maintenance request is proposal-only. Do not edit repository
files, run a formatter that writes, stage Git changes, or promote a draft to reviewed.
Return a complete proposal using references/proposal-template.md, then stop for explicit
human confirmation.
A later message counts as confirmation only when the human identifies the proposal or exact diff and explicitly asks to apply it. General encouragement, an ordinary analysis request, silence, or an Agent/sub-Agent message is not confirmation. After confirmation, apply only the approved scope; any material source conflict or changed diff requires a new proposal and a new confirmation.
Proposal workflow
- State the maintenance question, affected knowledge IDs/weapon IDs, and why a formal corpus change may be needed.
- Read the existing documents and source registry. Search reviewed knowledge first so the proposal does not duplicate or contradict an active entry.
- Research current authoritative sources. Prefer official patch notes and pinned machine-readable facts; use community mechanics pages only with publisher, retrieval date, scope and limitations. Do not use popularity, model memory, or an unsourced build as evidence.
- Separate stable weapon facts, volatile mechanics, build candidates, and Agent inference. A weapon profile may teach how to generate and test candidates; it must not freeze one global best build, element combination, replacement slot or recommendation.
- Draft exact source-registry and Markdown changes. Include source IDs, URLs, publisher, retrieval date, version note, validity interval, review status, weapon scope and every important conflict or exclusion.
- List the reason for each changed claim and a readable before/after diff. Include migration impact on facts, MCP contracts, retrieval evaluation and player reports.
- Specify tests: schema/front-matter validation, source-reference integrity, retrieval cases, weapon applicability, contradiction checks and any full regression required.
- End with
等待人工确认：未写入知识库. Do not call the proposal approved yourself.
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.
- 7d ago First seen · 69 lines · 48 tokens per session scan A d361f8ea41aa
riven-knowledge-maintainer is a skill published in the GitHub repository ruali-dev/Riven-Analyst (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 769 once invoked, about $0.0002 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
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
test-review
Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.