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/levifig/rails-instructions/rails-deploymentgit clone --depth 1 https://github.com/levifig/rails-instructionsWrote 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/levifig/rails-instructions/rails-deployment)<a href="https://agentmods.dev/instructions/levifig/rails-instructions/rails-deployment"><img src="https://agentmods.dev/badge/instructions/levifig/rails-instructions/rails-deployment.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 | $0.00978 | $0.00978 |
| Opus 5 | $0.00489 | $0.00489 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
rails-instructions rails-deployment.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 5d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Deployment with Kamal
Core Philosophy
- Deploy containerized Rails applications without complexity
- Use Kamal for zero-downtime deployments
- Keep deployment configuration simple and version controlled
- Leverage Docker without becoming a Docker expert
- Deploy anywhere with SSH access
Kamal Principles
- One command deployments with automatic rollback
- Built-in health checks and rolling updates
- Integrated secret management
- No Kubernetes complexity needed
- Direct SSH-based deployment to servers
Configuration Strategy
- Keep all deployment config in
config/deploy.yml - Use environment-specific settings wisely
- Store secrets securely with Kamal's encryption
- Version control deployment configuration
- Document server requirements clearly
Server Prerequisites
- Ensure servers have Docker installed
- Configure SSH access for deployment user
- Set up firewall rules appropriately
- Prepare SSL certificates if needed
- Verify sufficient disk space and memory
Environment Management
- Use Kamal's built-in environment variable handling
- Separate secrets from non-sensitive configuration
- Use
.envfiles for local development only - Leverage Rails credentials for application secrets
- Keep production passwords out of version control
Container Strategy
- Build minimal production Docker images
- Use multi-stage builds to reduce size
- Install only production dependencies
- Configure proper health check endpoints
- Set appropriate resource limits
Database Configuration
- Use managed databases when possible
- Configure connection pooling appropriately
- Set up automated backups
- Use read replicas for scaling
- Handle database migrations carefully
Asset Management
- Precompile assets during Docker build
- Use CDN for asset delivery
- Configure proper cache headers
- Compress assets appropriately
- Handle asset versioning correctly
Health Checks
- Implement
/upendpoint for health monitoring - Check database connectivity
- Verify background job processing
- Monitor external service dependencies
- Return appropriate status codes
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.
- 5d ago First seen · 201 lines · 978 tokens per session scan A ed5620618852
rails-instructions rails-deployment.instructions.md is an instructions file published in the GitHub repository levifig/rails-instructions (54 stars, last pushed 1y ago), licensed MIT. It adds 978 tokens to every session, about $0.0049 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
timoni AGENTS.md
AGENTS.md instructions for stefanprodan/timoni, covering agents.md, what timoni is, common commands, architecture and cmd/timoni/ — cli (cobra).
selfhost-ai CLAUDE.md
Claude Code instructions for kossakovsky/selfhost-ai, covering claude.md, project overview, core architecture, key files and installation flow.
aks-mcp copilot-instructions.md
Instructions for Azure/aks-mcp, covering copilot instructions, project overview, architecture, high-level structure and key components.
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge landing-zone.instructions.md
Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.
rosetta republish-assets-not-npm.instructions.md
Instructions for tikoci/rosetta: The republishassets workflow input is for GitHub Release assets and OCI tags only.