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/LarouexNonprofitConsulting/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/larouexnonprofitconsulting/larouex-fullstack-plugin/deploy-azure-production)<a href="https://agentmods.dev/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/deploy-azure-production"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/deploy-azure-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.00262 |
| Opus 5 | $0.00000 | $0.00131 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
deploy-azure-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- deploy-azure-production — 100% identical, 0 lines differ
What it actually says
Deploy to Azure production with mandatory review gate and comprehensive 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
- Validate environment variables for production
- Validate Application Insights is configured and monitoring enabled
- Build Next.js with production optimizations
- Create deployment snapshot/backup point
- Deploy to production slot with slot swap preview
- Perform slot swap from staging to production
- Monitor Application Insights for errors (5-minute window)
- Verify production endpoints and health checks
- Provide rollback instructions with slot swap revert commands
Include pre-deployment checklist, post-deployment verification, and monitoring dashboard 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.
- 5d ago First seen · 25 lines · 0 tokens per session scan A 630623255aa5
deploy-azure-production is a command published in the GitHub repository LarouexNonprofitConsulting/larouex-fullstack-plugin (8 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 262 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-09-03.
Other commands, from other repositories
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.
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-websockets-azure
Implement real-time communication using Azure SignalR Service. Set up Azure SignalR resource and obtain connection string. Create Azure Function for SignalR negotiation endpoint. Implement SignalR hub with message broadcasting methods. Create client connection hooks with automatic reconnection. Implement…