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/ruali-dev/riven-analyst/confignpx skills add ruali-dev/Riven-Analyst --skill configgit 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/config)<a href="https://agentmods.dev/skills/ruali-dev/riven-analyst/config"><img src="https://agentmods.dev/badge/skills/ruali-dev/riven-analyst/config.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.00034 | $0.00266 |
| Opus 5 | $0.00017 | $0.00133 |
| Sonnet 5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
config 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 3d 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.
What it actually says
Riven Analyst Config
Change only the requested option and preserve the installation scope and unrelated Claude settings.
- Summarize the current requested change: Provider fields, web research, or permission scope. Screenshot directories remain a host-level, per-session permission and are not plugin config.
- On Claude Code, open the native Riven Analyst plugin configuration for all option changes. On Codex, use the host's MCP environment configuration. Sensitive API keys must stay in masked or environment-backed secret storage; never request or repeat them in chat.
- When enabling external vision or bounded web research for the first time, read
../setup/SKILL.mdand use its permission preview/apply sequence. Existing permissions need not be rewritten when only a model name, endpoint, or key changes. - Ask Claude Code to
/reload-plugins, or start a new Codex task, then state what changed without exposing secret values.
Do not create a second config file, edit the plugin cache, run broad diagnostics, or silently alter the plugin installation scope.
What ships with it
1 file 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.
- 3d ago First seen · 23 lines · 34 tokens per session scan A 16db785bd347
config is a skill published in the GitHub repository ruali-dev/Riven-Analyst (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 266 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.
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.
codex-implement
Implement features via Codex MCP. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.
invest-backup
Back up / restore openInvest's local state — memory/ (holdings, strategy, user profile, committee records, dream logs) + db/ (trade ledger, job run history, market-data cache) + .env (SMTP/API credentials) + userprofile.json. All of this data is .gitignore'd with no historical versions in git, so a single accidental…
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
agentic-workflow-audit
Use when reviewing or auditing an existing agent / LLM-pipeline architecture — e.g. 'is my workflow actually decomposed or secretly a mega-agent?', 'are my task boundaries and success criteria right?' — even without the word 'audit'. ｜ 要檢視／review／稽核既有 agent 或 LLM pipeline 的架構，或問「有沒有拆好」「是不是變成 mega agent」「task…