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 rules/felipebarcelospro/igniter-js/igniter-advanced-featuresgit 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/igniter-advanced-features)<a href="https://agentmods.dev/rules/felipebarcelospro/igniter-js/igniter-advanced-features"><img src="https://agentmods.dev/badge/rules/felipebarcelospro/igniter-js/igniter-advanced-features.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 | $0.00039 | $0.01473 |
| Opus 5 | $0.00019 | $0.00737 |
| Sonnet 5 | $0.00008 | $0.00295 |
| Haiku 4.5 | $0.00004 | $0.00147 |
Grade A, and why
igniter-advanced-features 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 3d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Igniter.js: Advanced Features
This guide covers the advanced, production-grade features of Igniter.js that enable complex, scalable application development.
1. Background Jobs (BullMQ)
The jobs system allows you to offload long-running or resource-intensive tasks to a separate background worker process, preventing API requests from timing out and improving user experience.
1.1. Defining a Job
Jobs are defined in a dedicated job router file. Each job has a unique name, a Zod schema for its input, and a handler function.
- File Location:
src/providers/jobs.ts(or a similar central location)
// src/providers/jobs.ts
import { jobs } from '@/igniter';
import { z } from 'zod';
export const emailJobs = jobs.router({
sendWelcomeEmail: jobs.register({
// Zod schema for type-safe job inputs
input: z.object({
userId: z.string(),
}),
// The handler that performs the background work
handler: async ({ input, context }) => {
const user = await context.database.user.findUnique({ where: { id: input.userId } });
if (user) {
await context.mail.send({
to: user.email,
template: 'welcome',
data: { name: user.name },
});
}
},
}),
});
export const REGISTERED_JOBS = {
emails: emailJobs,
};
1.2. Enqueuing a Job
Jobs are typically enqueued from within a mutation handler. The API call returns immediately to the user while the job is processed in the background.
// In a controller
createUser: igniter.mutation({
// ...
handler: async ({ request, context, response }) => {
const newUser = await context.database.user.create({ data: request.body });
// Schedule the job to run in the background
await igniter.jobs.emails.schedule({
task: 'sendWelcomeEmail',
input: { userId: newUser.id }, // Type-checked against the job's Zod schema
});
return response.created(newUser);
}
})
2. Store (Redis)
The store provides a high-performance, Redis-backed key-value store for caching and pub/sub messaging.
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.
- 3d ago First seen · 192 lines · 39 tokens per session scan A 5aa55d9ad62c
igniter-advanced-features is a cursor rule published in the GitHub repository felipebarcelospro/igniter-js (242 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,473 once invoked, about $0.0002 per session on Opus 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
codegraph
CodeGraph MCP usage guide — when to use which tool.
git
Never mutate git history, remotes, or GitHub repo state.
css
TSF stylesheet conventions, layout debugging, and minification.
javascript
TSF JavaScript syntax, formatting, and minification.
local
Private workspace guidance and gitignored .local search (Grep/Glob are blind).
docs
Readme wording constraints, WordPress readme format, changelog prose style, and public API naming requirements.