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.
git 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/commands/maquina-app/rails-claude-code/sdd-discover-standards)<a href="https://agentmods.dev/commands/maquina-app/rails-claude-code/sdd-discover-standards"><img src="https://agentmods.dev/badge/commands/maquina-app/rails-claude-code/sdd-discover-standards/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/commands/maquina-app/rails-claude-code/sdd-discover-standards"><img src="https://agentmods.dev/badge/commands/maquina-app/rails-claude-code/sdd-discover-standards.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.00014 | $0.00355 |
| Opus 5 | $0.00007 | $0.00178 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
sdd-discover-standards 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 10d 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.
What it actually says
Discover and document tribal knowledge from this Rails codebase as new SDD standards.
Use this when adding SDD to an existing Rails app to capture patterns beyond the bootstrapped defaults.
Process
1. Identify focus area
If the user specified an area, use it. Otherwise, analyze the codebase and suggest 3–5 areas:
- Models (naming, scopes, concerns, validations)
- Controllers (authorization, response patterns, filters)
- Views (component usage, partial conventions, i18n)
- Jobs / mailers / concerns (shared patterns)
- Tests (fixture conventions, helper patterns)
Present options and ask which to focus on first.
2. Analyze files in that area
Read 5–10 representative files. Look for patterns that are:
- Opinionated — a deliberate choice that could have gone differently
- Tribal — something a new developer wouldn't know without being told
- Consistent — repeated across multiple files
3. For each pattern found
Ask the user 1–2 questions:
- "What problem does this solve?"
- "Are there exceptions?"
Then draft a concise standard and confirm before writing the file.
4. Write the standard file
Save to sdd/standards/[area]/[name].md — concise, scannable, leads with the rule.
5. Update index.yml
Add the new entry to sdd/standards/index.yml with file path, description, and applies_to.
Only document what's non-obvious. Rails defaults don't need documenting.
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.
- 10d ago First seen · 42 lines · 14 tokens per session scan A 8f2d3550cc06
sdd-discover-standards is a command published in the GitHub repository maquina-app/rails-claude-code (47 stars, last pushed 25d ago), licensed MIT. It adds 14 tokens to every session and 355 once invoked, about $0.0001 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 commands, from other repositories
initialize-ruby
Manual override: initialize ast-index for Ruby/Rails project.
review-ruby-code
Review Ruby/Rails code with Sandi Metz rules and SOLID principles.
write-inline-rbs
Write inline RBS type annotations in Ruby source files using rbs-inline comment syntax.
write-rbs
Write standalone RBS type signatures for Ruby files. Analyzes code, finds tests, traces types, and generates sig/.rbs files.
rails-review
Ruby on Rails code review with severity-based filtering.
sinatra-test
Generate comprehensive tests for Sinatra routes, middleware, and helpers using RSpec or Minitest.