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 rysh-ai/rysh-cli-code --skill docs-link-checkergit clone --depth 1 https://github.com/rysh-ai/rysh-cli-codeWrote 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/rysh-ai/rysh-cli-code/docs-link-checker)<a href="https://agentmods.dev/skills/rysh-ai/rysh-cli-code/docs-link-checker"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/docs-link-checker/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/rysh-ai/rysh-cli-code/docs-link-checker"><img src="https://agentmods.dev/badge/skills/rysh-ai/rysh-cli-code/docs-link-checker.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.00015 | $0.00378 |
| Opus 5.5 | $0.00006 | $0.00151 |
| Sonnet 5.5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
docs-link-checker 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 1mo 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
You are checking the documentation site at {{start_url}} for broken links, using only the browser (browser_action). Never run shell commands.
Method
- Navigate to {{start_url}}. Use get_elements to collect every link in the site's navigation (sidebar, header, footer) plus in-page links that stay on the same host. External links are out of scope — note them, skip them.
- Visit each collected link once (navigate). Keep a visited list so you
never re-check a URL. For each page record one verdict:
- OK — the page renders with real content.
- BROKEN — an error page (404/500, "page not found") or a navigation failure.
- EMPTY — the page loads but get_text shows no meaningful body (a bare template, a "TODO" stub).
- On each OK page, also collect same-host links you have not seen yet, up to a total of 50 pages checked. Stop at the cap and say the crawl was truncated.
Report
Finish with a summary the reader can act on:
checked N links: X ok, Y broken, Z empty- One line per BROKEN or EMPTY page: the URL, the page that linked to it, and the verdict.
- If everything passed: "all links ok" plus the count.
Verdicts must come from pages you actually visited in this run — never guess a status from the URL shape.
What ships with it
3 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.
- 1mo ago First seen · 42 lines · 15 tokens per session scan A 55917bf6cef9
docs-link-checker is a skill published in the GitHub repository rysh-ai/rysh-cli-code (5 stars, last pushed 11d ago), licensed Apache-2.0. It adds 15 tokens to every session and 378 once invoked, about $0.0001 per session on Opus 5.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
web
Read the public web: search for sources, read one page as Markdown, and run site scripts for structured records (X/Twitter via FxEmbed, Exa search, GitHub, Hacker News, Reddit, Wikipedia, Bilibili bundled; a catalog of more installable with one command). Use for any task that needs something from a public website: a…
browser-use
Control the user's Chrome through the existing persistent Node REPL and the Qwen Browser SDK.
harbor-daytona
Use Harbor's Daytona sandbox platform for computer use — creating sandboxes, taking screenshots, sending mouse/keyboard input, and building agent loops. Use when the user wants to interact with a GUI, automate a desktop, do computer use, control a browser visually, or run Claude computer use against a Daytona sandbox.
ketch
Research skill for ketch — a fast stateless CLI for web search, OSS code search, curated library docs, page scraping, and site crawling; an optional MCP server exists for operators who want it, but the CLI is the primary interface. Use when a question needs live sources: 'research X', 'what are people saying about Y'…
weknora-shared
Use when driving a WeKnora RAG server through the weknora CLI as an agent — authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes. Read this before any other weknora- skill.
weknora-rag-search
Use when retrieving from or asking questions against a WeKnora knowledge base via the weknora CLI — and especially when unsure whether to use chat, session ask, or search chunks for a given goal.