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/web-infra-dev/rsdoctor/rstack-cli-docsnpx skills add web-infra-dev/rsdoctor --skill rstack-cli-docsgit clone --depth 1 https://github.com/web-infra-dev/rsdoctorWhat 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.00057 | $0.00302 |
| Opus 5 | $0.00028 | $0.00151 |
| Sonnet 5 | $0.00011 | $0.00060 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
rstack-cli-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 2d 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
Rstack CLI Docs
Rstack CLI is the rstack package, exposed through the rs binaries. It provides one CLI, one
config file, and a consistent workflow for the Rstack JavaScript toolchain.
It covers web app, library, docs, test, lint, formatting, Git hook, and staged-file workflows.
Read installed docs when this skill applies
When this skill applies, find and read the relevant Markdown documentation shipped with the installed rstack package.
Model knowledge can be outdated; the installed documentation is the source of truth for the project's Rstack version.
-
Start with
node_modules/rstack/docs/llms.txt, then read only the linked pages relevant to the task before proposing or making changes. -
For exact CLI flags and behavior, also run
rs -horrs <command> -hwhen supported.
If the bundled docs are not available at that path, locate the installed rstack package.
If they are still unavailable, verify that rstack is installed, and use CLI help plus the online Rstack documentation as a fallback.
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.
- 2d ago First seen · 26 lines · 57 tokens per session scan A 134be0809477
rstack-cli-docs is a skill published in the GitHub repository web-infra-dev/rsdoctor (1,139 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 302 once invoked, about $0.0003 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
resume-builder
Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON…
dependency-flow
MAUI-specific dependency flow rules, channel conventions, and feed lookup workflows. Use when asked about darc, BAR, Maestro, feeds for .NET MAUI, build promotion, asset lookup, channel mappings, or dependency flow for dotnet/maui. Wraps the maestro-cli skill and maestro MCP tools with MAUI-specific guardrails.
pr-finalize
Finalizes any PR for merge by verifying title/description match implementation AND performing code review for best practices. Use when asked to "finalize PR", "check PR description", "review commit message", before merging any PR, or when PR implementation changed during review. Do NOT use for extracting lessons (use…
evaluate-pr-tests
Evaluates tests added in a PR for coverage, quality, edge cases, and test type appropriateness. Checks if tests cover the fix, finds gaps, and recommends lighter test types when possible. Prefer unit tests over device tests over UI tests. Triggers on: 'evaluate tests in PR', 'review test quality', 'are these tests…
verify-tests-fail-without-fix
Verifies tests catch the bug. Auto-detects test type (UI tests, device tests, unit tests) and dispatches to the appropriate runner. Supports two modes - verify failure only (test creation) or full verification (test + fix validation).
write-ui-tests
Creates UI tests for a GitHub issue and verifies they reproduce the bug. Iterates until tests actually fail (proving they catch the issue). Use when PR lacks tests or tests need to be created for an issue.