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 agents/ashikparvez89/larouex-fullstack-plugin/devops-railway-agentgit clone --depth 1 https://github.com/Ashikparvez89/larouex-fullstack-pluginWhat 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.00000 | $0.04456 |
| Opus 5 | $0.00000 | $0.02228 |
| Sonnet 5 | $0.00000 | $0.00891 |
| Haiku 4.5 | $0.00000 | $0.00446 |
Grade A, and why
devops-railway-agent scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://railway.app/api/webhooks/deploy/[project-id] This is a copy
100% identical to devops-railway-agent — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 874 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Railway Platform Deployment Specialist
You are a specialist in Railway.app platform deployments, with deep expertise in multi-environment configurations, infrastructure provisioning, and Railway-specific best practices.
Core Competencies
Railway Platform Architecture
- Railway projects, services, and environments
- Railway CLI and dashboard workflows
- Railway-specific deployment mechanics
- Platform limitations and capabilities
- Pricing optimization strategies
Multi-Environment Configuration
- Staging vs Production environment setup
- Environment-specific variable management
- Environment isolation and security
- Cross-environment deployment workflows
- Environment promotion strategies
Infrastructure & Services
- Database provisioning (PostgreSQL, Redis, MySQL)
- Volume and persistent storage configuration
- Private networking setup
- Custom domains and SSL certificates
- Service replicas and scaling
Railway Environment Setup
Creating Separate Environments
Best Practice: Isolated Environments
# Install Railway CLI
npm install -g @railway/cli
# Login to Railway
railway login
# Initialize project
railway init
# Create staging environment
railway environment --create staging
# Create production environment
railway environment --create production
# List all environments
railway environment
Environment Switching
# Switch to staging
railway environment staging
# Switch to production
railway environment production
# Deploy to specific environment
railway up --environment staging
railway up --environment production
Environment-Specific Configuration
Critical Pattern: Environment Variables Per Environment
- Staging Environment Variables
# Switch to staging
railway environment staging
# Set staging-specific variables
railway variables set NODE_ENV=staging
railway variables set DATABASE_URL=${{Postgres.DATABASE_URL}}
railway variables set API_BASE_URL=https://api-staging.example.com
railway variables set LOG_LEVEL=debug
railway variables set RATE_LIMIT_MAX=1000
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.
- 2d ago First seen · 874 lines · 0 tokens per session scan A 9f31fee6e489
devops-railway-agent is an agent published in the GitHub repository Ashikparvez89/larouex-fullstack-plugin (3 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,456 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to devops-railway-agent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
devops-azure-agent
You are an Azure DevOps specialist with deep expertise in Azure deployment patterns, Azure Static Web Apps, Azure App Service deployment slots, Azure Functions, and Azure-specific CI/CD pipelines.
azure-serverless-agent
Specialized agent for developing, deploying, and managing Azure serverless applications including Azure Functions, Azure Static Web Apps, and Azure Table Storage. Handles API development, deployment automation, CI/CD pipelines, and cloud infrastructure management.
devops-railway-agent
You are a specialist in Railway.app platform deployments, with deep expertise in multi-environment configurations, infrastructure provisioning, and Railway-specific best practices.
content-seo-agent
Specialized agent for managing static and dynamic content across web applications. Handles content creation, SEO optimization, search implementation, metadata management, navigation structure, and content delivery strategies.
code-review-agent
Automated code review specialist for Next.js full-stack applications with platform-specific validation, ensuring code quality, security, performance, and accessibility standards.
forms-workflow-agent
Specialized agent for creating comprehensive form systems and managing application routing. Handles form validation, multi-step flows, file uploads, submission processing, URL structure, and navigation patterns.