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/slbug/claude-ruby-grape-rails/docs-checknpx skills add slbug/claude-ruby-grape-rails --skill docs-checkgit clone --depth 1 https://github.com/slbug/claude-ruby-grape-railsWhat 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.00045 | $0.01644 |
| Opus 5 | $0.00023 | $0.00822 |
| Sonnet 5 | $0.00009 | $0.00329 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
docs-check 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Documentation Compatibility Check
Audience: Agents, Not Humans
Imperative-only. Validate plugins/ruby-grape-rails/ against current
cached Claude Code docs. Contributor maintenance — NOT user-facing.
When to Use
| Question | Answer this skill gives |
|---|---|
| Did Claude docs change in a way that breaks our plugin? | yes |
| Is this warning a real compatibility issue or stale local guidance? | yes |
| What new Claude feature is now documented and relevant? | yes |
| Is naming style / line count / repo preference unrelated to docs? | NO — out of scope |
Usage
| Command | Scope |
|---|---|
/docs-check |
all surfaces |
/docs-check --quick |
skip docs fetch, structural drift only |
/docs-check --focus=agents |
agents only |
/docs-check --focus=skills |
skills only |
/docs-check --focus=hooks |
hooks only |
/docs-check --focus=config |
plugin manifest + marketplace only |
Execution Flow
1. Run Deterministic Baseline
Run all three, in order, to catch structural schema issues without docs interpretation:
| Command | Covers |
|---|---|
claude plugin validate --strict plugins/ruby-grape-rails |
shipped plugin manifest + components |
claude plugin validate --strict . |
.claude-plugin/marketplace.json, which the plugin-directory run skips |
claude plugin validate --strict .claude |
contributor-only components under .claude/, validated as a bare component directory |
--strict promotes unrecognized-field and missing-metadata warnings to
errors. npm run validate runs the same three via
scripts/validate-plugin.sh; CI runs them as separate lint-job steps.
2. Refresh Cached Docs (Unless --quick)
From repo root: bash ./scripts/fetch-claude-docs.sh.
--quick skips fetching; limits run to structural drift checks against
existing cache.
3. Inventory Plugin Surfaces
Identify in-scope surfaces per --focus:
| Surface | Paths |
|---|---|
agents |
plugins/ruby-grape-rails/agents/*.md |
skills |
plugins/ruby-grape-rails/skills/*/SKILL.md |
hooks |
plugins/ruby-grape-rails/hooks/hooks.json |
config |
plugins/ruby-grape-rails/.claude-plugin/plugin.json, .claude-plugin/marketplace.json |
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.
- 2d ago First seen · 191 lines · 45 tokens per session scan A f0372e62945d
docs-check is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 1,644 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-buzz
This is a Hermes-native buzz workflow skill.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-api-detail-pack
Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.
redteam-postex-detail-pack
Domain routing and boundary guidance for authorized post-exploitation testing after initial access, including privilege escalation, persistence, lateral movement, data collection, and cleanup considerations. Use when a task belongs to the post-exploitation domain and needs scope, evidence, pivot, or exit criteria.