Borrowing it
Nothing to install: this file belongs to maquina-app/rails-claude-code. 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/maquina-app/rails-claude-code/main/CLAUDE.mdgit clone --depth 1 https://github.com/maquina-app/rails-claude-codeWrote 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/maquina-app/rails-claude-code/claude-md)<a href="https://agentmods.dev/instructions/maquina-app/rails-claude-code/claude-md"><img src="https://agentmods.dev/badge/instructions/maquina-app/rails-claude-code/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.00726 | $0.00726 |
| Opus 5 | $0.00363 | $0.00363 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
rails-claude-code 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 7d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Documentation-only plugin marketplace — no build system, test suite, linter, or CI. All content is Markdown, JSON, and YAML.
Plugin structure
.claude-plugin/marketplace.json ← Lists all plugins
<plugin-name>/.claude-plugin/plugin.json ← Plugin metadata
<plugin-name>/agents/<plugin-name>.md ← Capability as a single-file agent (most plugins)
<plugin-name>/skills/<name>/SKILL.md ← Capability as a skill bundle (+ scripts/) — e.g. rails-hotwire-driver
Supporting files go in references/, workflows/, examples/, templates/ within each plugin directory; a skill's helper scripts go in skills/<name>/scripts/ (keep .sh files executable — git ls-files -s should show mode 100755).
A capability can ship as either a single-file agents/*.md (the common convention here) or a skills/<name>/SKILL.md bundle. Both are valid.
Critical rules
Validate before committing
This repo has no traditional test suite, but claude plugin validate <plugin-dir> (and claude plugin validate . for the marketplace) IS the check — run it after any manifest/frontmatter change. Add --strict to catch unrecognized fields, missing metadata, and version mismatches. Bump a plugin's version whenever its content changes, or installed users won't receive the update (an unset version falls back to the git SHA).
Version sync
Versions must match in THREE places — update all or you'll create drift:
.claude-plugin/marketplace.json→versionfield for the plugin<plugin-name>/.claude-plugin/plugin.json→versionfield- The root
README.mdPlugins table version column (and confirm the install/enabledPluginsblocks list the plugin)
Install commands
The marketplace name is maquina, so install commands use the @maquina suffix (/plugin install <plugin>@maquina) — NOT @rails. The marketplace is added with the GitHub owner/repo: /plugin marketplace add maquina-app/rails-claude-code (owner is maquina-app, matching the git remote — not maquina). Keep these consistent across the root README and any per-plugin docs.
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.
- 7d ago First seen · 39 lines · 726 tokens per session scan A 7c3bb70109cc
rails-claude-code CLAUDE.md is an instructions file published in the GitHub repository maquina-app/rails-claude-code (47 stars, last pushed 21d ago), licensed MIT. It adds 726 tokens to every session, about $0.0036 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.