Borrowing it
Nothing to install: this file belongs to slbug/claude-ruby-grape-rails. 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/slbug/claude-ruby-grape-rails/main/.github/instructions/markdown-review.instructions.mdgit clone --depth 1 https://github.com/slbug/claude-ruby-grape-railsWrote 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/slbug/claude-ruby-grape-rails/markdown-review)<a href="https://agentmods.dev/instructions/slbug/claude-ruby-grape-rails/markdown-review"><img src="https://agentmods.dev/badge/instructions/slbug/claude-ruby-grape-rails/markdown-review/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/instructions/slbug/claude-ruby-grape-rails/markdown-review"><img src="https://agentmods.dev/badge/instructions/slbug/claude-ruby-grape-rails/markdown-review.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.01757 | $0.01757 |
| Opus 5.5 | $0.00703 | $0.00703 |
| Sonnet 5.5 | $0.00351 | $0.00351 |
| Haiku 4.5 | $0.00176 | $0.00176 |
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 25d 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 — 150 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, background (only with
context: fork), hooks, shell, metadata, license, compatibility. 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,
experimental.cacheTtl.
Plugin-shipped agents under plugins/**/agents/ are narrowed by the
plugin components reference
(https://code.claude.com/docs/en/plugins/components) to the subset
CC honors on plugin agents — do not add initialPrompt,
permissionMode, hooks, or mcpServers to plugin-shipped agents
(see plugin-review.instructions.md for the narrowed set).
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.
- 25d ago Changed · +3 lines · +44 tokens per session 8dacd541259f
- 1mo 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 26d ago), licensed MIT. It adds 1,757 tokens to every session, about $0.0070 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 instructions, from other repositories
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).