Borrowing it
Nothing to install: this file belongs to kieranklaassen/ruby_llm-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kieranklaassen/ruby_llm-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/kieranklaassen/ruby_llm-skillsWrote 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/kieranklaassen/ruby_llm-skills/claude-md)<a href="https://agentmods.dev/instructions/kieranklaassen/ruby_llm-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/kieranklaassen/ruby_llm-skills/claude-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.1 | $0.00961 | $0.00961 |
| Opus 5 | $0.00481 | $0.00481 |
| Sonnet 5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
ruby_llm-skills CLAUDE.md 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 8d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
RubyLLM::Skills is a Ruby gem that implements the Agent Skills specification for RubyLLM. It enables progressive disclosure of AI capabilities through a three-level pattern: metadata (~100 tokens), full instructions (SKILL.md), and on-demand resources (scripts, references, assets).
Development Commands
Setup
bin/setup # Install dependencies and prepare development environment
Testing
bundle exec rake test # Run all tests using Minitest
bundle exec rake # Run default task: tests + linting
Linting
bundle exec rake standard # Run StandardRB linter
bundle exec standardrb --fix # Auto-fix linting issues
Console
bin/console # Start IRB console with gem loaded
Gem Tasks
bundle exec rake build # Build gem to pkg/
bundle exec rake install # Build and install gem locally
bundle exec rake release # Build, tag, and push gem (requires credentials)
Architecture
Module Structure
The gem uses the RubyLLM::Skills namespace (matches the parent ruby_llm gem):
lib/ruby_llm/
├── skills.rb # Main module entry point
└── skills/
└── version.rb # Gem version constant
Key Design Patterns
Progressive Disclosure: Skills load in three stages to minimize context usage:
- Metadata (name + description) - loaded at startup, injected into system prompt
- Full instructions (SKILL.md) - loaded when LLM determines skill is relevant
- Resources (scripts, references, assets) - loaded on demand during execution
Multi-Source Loading: Skills can be loaded from:
- Filesystem directories (default:
app/skills) - Zip archives (for distribution)
- ActiveRecord models (for per-user customization)
- Multiple sources simultaneously (later sources override earlier ones)
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.
- 8d ago First seen · 128 lines · 961 tokens per session scan A dab4d96f9daf
ruby_llm-skills CLAUDE.md is an instructions file published in the GitHub repository kieranklaassen/ruby_llm-skills (34 stars, last pushed 5mo ago), licensed MIT. It adds 961 tokens to every session, about $0.0048 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.