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/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/migrate-azure-to-railway)<a href="https://agentmods.dev/commands/ashikparvez89/larouex-fullstack-plugin/migrate-azure-to-railway"><img src="https://agentmods.dev/badge/commands/ashikparvez89/larouex-fullstack-plugin/migrate-azure-to-railway/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/ashikparvez89/larouex-fullstack-plugin/migrate-azure-to-railway"><img src="https://agentmods.dev/badge/commands/ashikparvez89/larouex-fullstack-plugin/migrate-azure-to-railway.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.00110 |
| Opus 5 | $0.00000 | $0.00055 |
| Sonnet 5 | $0.00000 | $0.00022 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
migrate-azure-to-railway 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 6d 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 migrate-azure-to-railway — 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
Migrate this Azure-hosted project to Railway. Convert Azure Functions to Express.js API routes. Migrate Azure Table Storage to PostgreSQL with Prisma ORM. Update environment variables for Railway platform. Create railway.toml configuration and Dockerfile for deployment. Set up staging and production environments. Configure custom domains and SSL certificates. Migrate static web app configuration to Railway's routing. Update CI/CD pipelines for Railway deployment. Provide step-by-step migration checklist and deployment instructions. Reference devops-railway-agent for Railway-specific expertise. Test all functionality after migration.
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.
- 6d ago First seen · 2 lines · 0 tokens per session scan A ce8befed7e94
migrate-azure-to-railway is a command published in the GitHub repository Ashikparvez89/larouex-fullstack-plugin (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 110 tokens. A static security scan graded it A with 0 findings. It is 100% identical to migrate-azure-to-railway, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
review-before-deploy
Execute comprehensive pre-deployment review using code-review-agent with all relevant platform agents. Run complete deployment readiness checklist: verify all tests pass (unit, integration, E2E), security audit clean (no Critical/High issues), performance benchmarks met (Lighthouse > 90), TypeScript compilation…
migrate-azure-to-railway
Migrate this Azure-hosted project to Railway. Convert Azure Functions to Express.js API routes. Migrate Azure Table Storage to PostgreSQL with Prisma ORM. Update environment variables for Railway platform. Create railway.toml configuration and Dockerfile for deployment. Set up staging and production environments.…
migrate-railway-to-azure
Migrate this Railway-hosted project to Azure Static Web Apps. Convert Express API routes to Azure Functions with HTTP triggers. Migrate PostgreSQL database to Azure Table Storage or Azure SQL Database. Create staticwebapp.config.json for routing and configuration. Set up GitHub Actions workflow for Azure deployment.…
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.
review-api
Review an API endpoint using code-review-agent with azure-serverless-agent or devops-railway-agent based on deployment target. Analyze input validation (Zod schemas), authentication and authorization, rate limiting, CORS configuration, error handling with proper HTTP status codes, security vulnerabilities (SQL…