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/review-api)<a href="https://agentmods.dev/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/review-api"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/review-api/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/larouexnonprofitconsulting/larouex-fullstack-plugin/review-api"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/review-api.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.00141 |
| Opus 5.5 | $0.00000 | $0.00056 |
| Sonnet 5.5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
review-api 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 1mo 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:
- review-api — 100% identical, 0 lines differ
What it actually says
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 injection, XSS), database query optimization (N+1 prevention), response caching strategies, structured logging, and API documentation. Check platform-specific patterns: Azure Functions (host.json, bindings, Application Insights) or Express routes (middleware, error handlers). Provide security-focused recommendations with code examples. Specify the API file path after the command. Output includes critical security findings, performance optimizations, and compliance with REST/OpenAPI standards.
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.
- 1mo ago First seen · 2 lines · 0 tokens per session scan A 6f3f39a919bb
review-api is a command published in the GitHub repository LarouexNonprofitConsulting/larouex-fullstack-plugin (8 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 141 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
add-database-azure
Set up Azure Table Storage with complete data layer implementation.
add-seo
Add comprehensive SEO to a page using Next.js 15 Metadata API.
add-stripe
Integrate Stripe payment processing. Set up Stripe account and obtain API keys. Implement checkout flow using Stripe Checkout or Payment Element. Create payment API endpoints in Azure Functions or Express. Add webhook handling for payment events: succeeded, failed, refunded. Implement subscription billing with…
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…
add-websockets-railway
Implement WebSockets using Socket.io on Railway. Set up Socket.io server integrated with Express application. Configure CORS for WebSocket connections. Create client connection hooks with React. Implement room-based messaging for grouped communication. Add user authentication for WebSocket connections using JWT.…
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…