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 instructions/fdarian/rskills/agents-mdgit clone --depth 1 https://github.com/fdarian/rskillsWrote 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/instructions/fdarian/rskills/agents-md)<a href="https://agentmods.dev/instructions/fdarian/rskills/agents-md"><img src="https://agentmods.dev/badge/instructions/fdarian/rskills/agents-md.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.03586 | $0.03586 |
| Opus 5 | $0.01793 | $0.01793 |
| Sonnet 5 | $0.00717 | $0.00717 |
| Haiku 4.5 | $0.00359 | $0.00359 |
Grade B, and why
rskills AGENTS.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Honor `disableSkillShellExecution: true` in `<cwd>/.claude/settings.json` or `~/.claude/settings.json` — commands become `[shell command execution disabled by policy]`. How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rskills
A Bun + Effect.ts CLI for reading remote skills without installing them. Built on incur for the CLI surface.
What it does
rskills read <uri>— fetch a skill file and print markdown body content to stdout (frontmatter stripped by default;--rawreturns the literal file, no envelope, in any--format). Reading a directory URI exits non-zero with anIsDirectorymessage pointing torskills ls.rskills ls <uri>— list entries in a skill directory; returns structured{ entries: [{ name, type }] }(mirrors Anthropic'sls/Globtools —readis files-only,lsis directories)rskills search [query] [--source <name>] [--limit <n>]— search skills. On an interactive terminal (stdin + stdout both TTY, no--source, no--format/--json/--token-*), opens a live Ink picker: type to search (debounced 250 ms, race-safe via Effect fiber interruption), ↑/↓ to navigate, Enter for an action menu (read SKILL.md / copy identifier / copy install command / open on skills.sh), Esc to quit. Skills-sh only in interactive mode. Otherwise (piped,--format,--source, etc.) emits structured output — TOON by default, switchable via--format json|yaml|md|jsonl;queryis required in this mode.
URI scheme
<source>://<identifier>[/<subpath>] — <source>:// is optional; bare identifiers default to skills-sh://.
| Source | Identifier | Search? | Read? | List? |
|---|---|---|---|---|
skills-sh |
<owner>/<repo>/<skill-path> |
✓ (skills.sh API) | ✓ (5-step cascade: GitHub raw → skills.sh download → GitHub Trees API → unpkg → skills.sh page) | ✓ (GitHub Contents API, or the downloaded file set directly, against resolved root) |
github |
<owner>/<repo>/<path> |
— | ✓ (raw.githubusercontent.com) | ✓ (GitHub Contents API) |
well-known |
<host-or-base-url> |
✓ (fetches /.well-known/skills/index.json) |
✓ | ✓ (derives from files array in index; NotFound if no files) |
https |
full https://…md URL |
— | ✓ (must end in .md) |
— |
claude |
<skill-name> (single segment) |
— | ✓ (local filesystem) | ✓ |
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 · 195 lines · 3,586 tokens per session scan B 55db740e3f00
rskills AGENTS.md is an instructions file published in the GitHub repository fdarian/rskills (2 stars, last pushed 15d ago), licensed Apache-2.0. It adds 3,586 tokens to every session, about $0.0179 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.