Active Storage Validations is a Ruby gem for adding validation rules to files attached through Rails Active Storage. Rails developers use it to check whether uploaded images, videos, audio files, PDFs, and other attachments meet requirements such as type, size, dimensions, duration, or quantity.
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/igorkasyanchuk/active_storage_validationsWrote 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/rules/igorkasyanchuk/active_storage_validations/spec-integration)<a href="https://agentmods.dev/rules/igorkasyanchuk/active_storage_validations/spec-integration"><img src="https://agentmods.dev/badge/rules/igorkasyanchuk/active_storage_validations/spec-integration/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/rules/igorkasyanchuk/active_storage_validations/spec-integration"><img src="https://agentmods.dev/badge/rules/igorkasyanchuk/active_storage_validations/spec-integration.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.00000 | $0.00244 |
| Opus 5.5 | $0.00000 | $0.00098 |
| Sonnet 5.5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
spec-integration 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 1mo 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
Integration specs
- Follow shared conventions in
spec.mdc(namedsubject,describe/context,described_class).
Use integration specs only for behavior that unit/validator specs cannot express cleanly:
- Several validators stacked on one model (especially legacy demo models with
proc_*twins) - Cross-validator interactions (metadata cache sharing, Proc options based on another attachment property, nested attributes)
- Persistence lifecycles (attach → save → purge → reload blob counts)
- Cross-cutting fail-closed timeout behavior →
spec/validators/integration/command_timeout_spec.rb(not a single-validator file)
Do not duplicate single-validator option matrices here — those belong in spec/validators/*_spec.rb via shared examples.
Prefer focused, named examples over one giant smoke file. When removing an old smoke assertion, confirm coverage exists elsewhere first.
Use describe for named units/topics (User presence, #less_than) and context for situations (when …, with …, without …).
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.
- 1mo ago First seen · 23 lines · 0 tokens per session scan A 9e227cd09983
spec-integration is a cursor rule published in the GitHub repository igorkasyanchuk/active_storage_validations (1,193 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 244 tokens. 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 cursor rules, from other repositories
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.