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/slbug/claude-ruby-grape-rails/markdown-reviewgit 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.01713 | $0.01713 |
| Opus 5 | $0.00856 | $0.00856 |
| Sonnet 5 | $0.00343 | $0.00343 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
claude-ruby-grape-rails markdown-review.instructions.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 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown File Review Rules
Audience: Agents, Not Humans
Markdown in this repo loads into agent context at runtime. Flag prose that violates the imperative-only rule:
- Tutorial narration ("first do X, then Y, this teaches…") → flag
- Reasoning preludes before commands → flag
#thinking/checklist lines inside Bash command bodies (preference #6) → flag, suggest markdown table or prose lead-in- Long explanatory paragraphs where a table fits → flag
Exception files (human-facing, narrative OK): README.md,
CHANGELOG.md, files under scripts/ (executable code), files
under lab/eval/ (test fixtures).
Skill and Agent Frontmatter
Files under plugins/**/skills/ and plugins/**/agents/ use YAML
frontmatter between --- delimiters. This is Claude Code plugin syntax,
not standard markdown metadata.
Valid frontmatter fields for skills: name, description (single field
per agentskills.io canon — no when_to_use), argument-hint, arguments,
effort, disable-model-invocation, user-invocable, allowed-tools,
disallowed-tools, model, context, agent, hooks, shell. The paths: field is documented in CC
skill schema but empirically non-functional at plugin scope; do NOT
add it to plugin SKILL.md (project-level .claude/rules/*.md paths:
remains functional and is a separate mechanism).
Valid frontmatter fields for agents (general subagent surface, see
https://docs.claude.com/en/docs/claude-code/sub-agents): name,
description, model, effort, maxTurns, tools, disallowedTools, skills,
memory, background, isolation, omitClaudeMd, color, initialPrompt.
Plugin-shipped agents under plugins/**/agents/ are narrowed by the
plugins reference
(https://docs.claude.com/en/docs/claude-code/plugins-reference) to
the subset CC honors on plugin agents — do not add color or
initialPrompt to plugin-shipped agents (see
plugin-review.instructions.md for the narrowed set).
Runtime Variables
These are NOT errors — they are resolved at runtime by Claude Code:
${CLAUDE_SKILL_DIR}— path to the skill's own directory${CLAUDE_PLUGIN_ROOT}— path to the plugin root${CLAUDE_PLUGIN_DATA}— persistent plugin data directory
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 · 147 lines · 1,713 tokens per session scan A 490256e8e1d9
claude-ruby-grape-rails markdown-review.instructions.md is an instructions file published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 3d ago), licensed MIT. It adds 1,713 tokens to every session, about $0.0086 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 instructions, from other repositories
autotask-mcp dev_workflow.instructions.md
Guide for using Taskmaster to manage task-driven development workflows.
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
foggy-data-mcp-bridge-python CLAUDE.md
Instructions for foggy-projects/foggy-data-mcp-bridge-python, covering foggy data mcp bridge — python, 快速启动, 安装依赖, 运行测试 and 启动 mcp 服务（连接 docker mysql）.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.