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 commands/ashikparvez89/larouex-fullstack-plugin/deploy-railway-productiongit clone --depth 1 https://github.com/Ashikparvez89/larouex-fullstack-pluginWrote 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/ashikparvez89/larouex-fullstack-plugin/deploy-railway-production)<a href="https://agentmods.dev/commands/ashikparvez89/larouex-fullstack-plugin/deploy-railway-production"><img src="https://agentmods.dev/badge/commands/ashikparvez89/larouex-fullstack-plugin/deploy-railway-production.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.00000 | $0.00266 |
| Opus 5 | $0.00000 | $0.00133 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
deploy-railway-production 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 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.
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.
This is a copy
100% identical to deploy-railway-production — 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.
What it actually says
Deploy to Railway production environment with mandatory review gate and validation.
MANDATORY PRE-DEPLOYMENT REVIEW GATE:
- Execute /review-before-deploy command FIRST
- Review must show NO Critical or High severity issues
- Require explicit manual confirmation: "I have reviewed the findings and approve deployment to production"
- STOP DEPLOYMENT if review is not completed or issues are unresolved
WARNING: Deploying to production without completing the review gate bypasses critical safety checks for security vulnerabilities, performance issues, accessibility compliance, and configuration errors. This may result in production incidents, data exposure, or service degradation.
Execute production deployment pipeline ONLY after review approval:
- Run full test suite (unit, integration, e2e) and verify all pass
- Check staging deployment status and health
- Switch to production environment (railway environment production)
- Validate environment variables for production
- Validate monitoring and logging is configured (Railway logs, health endpoints)
- Create database backup before deployment
- Deploy services to production using Railway CLI
- Run database migrations on production database
- Monitor Railway logs for errors (5-minute window)
- Verify production endpoints and health checks
- Provide rollback instructions with previous deployment ID
Include pre-deployment checklist, post-deployment verification, and Railway dashboard monitoring links. Stop deployment if any validation fails.
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 · 25 lines · 0 tokens per session scan A d77baee7670e
deploy-railway-production is a command published in the GitHub repository Ashikparvez89/larouex-fullstack-plugin (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 266 tokens. A static security scan graded it A with 0 findings. It is 100% identical to deploy-railway-production, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
deploy-azure-production
Deploy to Azure production with mandatory review gate and comprehensive validation.
deploy-railway-production
Deploy to Railway production environment with mandatory review gate and validation.
setup-monitoring-azure
Configure comprehensive Azure Application Insights monitoring.
add-api-azure
Create a new Azure Function HTTP endpoint with full integration.
add-cron-azure
Create scheduled background jobs using Azure Functions timer triggers. Implement timer-triggered function with NCRONTAB expression for scheduling. Add comprehensive logging for job execution with Application Insights. Handle execution failures with error notifications. Implement idempotency to prevent duplicate…
add-search-azure
Integrate Azure Cognitive Search for powerful full-text search. Set up Azure Cognitive Search service and create search index with schema. Create Azure Function for search API endpoint with query parameters. Implement search component with filters and facets. Add autocomplete and suggestions using search service…