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/felipebarcelospro/igniter-jsWrote 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/rules/felipebarcelospro/igniter-js/middleware)<a href="https://agentmods.dev/rules/felipebarcelospro/igniter-js/middleware"><img src="https://agentmods.dev/badge/rules/felipebarcelospro/igniter-js/middleware/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/rules/felipebarcelospro/igniter-js/middleware"><img src="https://agentmods.dev/badge/rules/felipebarcelospro/igniter-js/middleware.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.00014 | $0.01919 |
| Opus 5.5 | $0.00006 | $0.00768 |
| Sonnet 5.5 | $0.00003 | $0.00384 |
| Haiku 4.5 | $0.00001 | $0.00192 |
Grade A, and why
middleware 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.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Middleware: Patterns & Best Practices
This guide provides the correct and validated patterns for creating and using Next.js Middleware within this project. The primary goal is to clearly separate concerns: Middleware handles routing and edge logic, while Igniter.js procedures handle backend business logic.
1. Core Principles
1.1. Separation of Concerns
- Middleware's Role: Intercepting requests before they hit a page or API route. Its responsibility is to handle routing, authentication checks, redirects, and request/response enrichment. It acts as a gatekeeper.
- Procedure's Role: Executing complex backend business logic. This is where database queries, integrations with other services, and heavy computations should live.
- CRITICAL RULE: Middleware should NEVER perform heavy database operations. It can make fast API calls (like checking a session), but any complex logic must be delegated to an API endpoint that uses a procedure.
1.2. Performance: Edge vs. Node.js Runtime
- Next.js 16 allows middleware to run in either the
edgeornodejsruntime. - Edge Runtime (Default & Recommended): Faster, runs closer to the user, but has limitations (e.g., no native Node.js APIs). Ideal for simple checks and redirects.
- Node.js Runtime: Provides full Node.js API compatibility. Use this only if you absolutely need a specific Node.js API that the Edge runtime doesn't support. For this project, we will stick to the Edge runtime unless there's a compelling reason to change. The existing
middleware.tsis already configured fornodejs, which is fine, but we should be mindful of its performance implications.
1.3. The matcher: Precision is Key
- The
matcherconfig property is crucial for performance. It defines exactly which paths will trigger the middleware. - An effective
matcherprevents the middleware from running unnecessarily on static assets, image optimization requests, or API routes. The existing configuration insrc/proxy.tsis a great example of this.
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 · 213 lines · 14 tokens per session scan A 9dfb75ff0dd8
middleware is a cursor rule published in the GitHub repository felipebarcelospro/igniter-js (241 stars, last pushed 9d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,919 once invoked, about $0.0001 per session on Opus 5.5. 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-01.
Other cursor rules, from other repositories
design-standards
API design standards, HTTP status codes, error handling, and client usage patterns.
lap
LAP CLI -- search, download, and install API specs for AI agents. Use when user needs an API (Stripe, Plaid, Twilio, etc). Commands: (1) npx -y @lap-platform/lapsh search , (2) npx -y @lap-platform/lapsh get -o .lap, (3) npx -y @lap-platform/lapsh skill-install --target cursor. The .lap file IS the spec -- do NOT…
nestjs-api
Cursor rule "nestjs-api" from WellApp-ai/Well, covering api rules (nestjs), module structure, patterns, controllers and dtos with validation.
git
Never mutate git history, remotes, or GitHub repo state.
css
TSF stylesheet conventions, layout debugging, and minification.
200-api-design
200: RESTful API design principles and patterns.