igniter-controllers

A focused guide on creating Igniter.js controllers and actions (queries and mutations). This rule details the properties, validation layers (Zod and Ensure), and the response object for building API endpoints.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/felipebarcelospro/igniter-js/igniter-controllers
Clone the repo
git clone --depth 1 https://github.com/felipebarcelospro/igniter-js

Made for: Cursor.

Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,335 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.01335
Opus 5 $0.00019 $0.00668
Sonnet 5 $0.00008 $0.00267
Haiku 4.5 $0.00004 $0.00134

Measured today against content hash 4f66c2c322fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

igniter-controllers 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 today.

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.

apps/sample-realtime-chat/.cursor/rules/igniter-controllers.mdc · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Igniter.js: Controllers and Actions

This guide provides a detailed reference for creating controllers and actions, which are the fundamental building blocks of an Igniter.js API.

1. Controllers (igniter.controller)

A controller is a logical grouping of related API actions under a common base path.

1.1. Definition

export const postsController = igniter.controller({
  name: 'Posts', // A descriptive name for documentation and debugging
  path: '/posts', // The base URL path for all actions in this controller
  actions: {
    // ... actions are defined here
  },
});

1.2. Controller Properties

Property Type Required Description
name string Yes A descriptive name for the controller, used in documentation.
path string Yes The base URL segment for all actions within this controller (e.g., /posts).
actions object Yes An object containing all the API endpoints (actions) for this controller.

2. Actions (igniter.query & igniter.mutation)

Actions are the individual API endpoints within a controller.

2.1. Query Actions (igniter.query)

Used for fetching data, corresponding to GET requests.

list: igniter.query({
  path: '/', // Final path: /posts/
  query: z.object({ // Zod schema for URL query parameter validation
    limit: z.string().optional(),
  }),
  handler: ({ request, response, context }) => {
    // ... business logic
  },
})

2.2. Mutation Actions (igniter.mutation)

Used for creating, updating, or deleting data. Corresponds to POST, PUT, PATCH, or DELETE requests.

create: igniter.mutation({
  path: '/', // Final path: /posts/
  method: 'POST', // Explicitly define the HTTP method
  body: z.object({ // Zod schema for request body validation
    title: z.string(),
    content: z.string(),
  }),
  handler: ({ request, response, context }) => {
    // ... business logic
  },
})

Read the full file on GitHub · 138 lines

Changes

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.

  1. today First seen · 138 lines · 39 tokens per session scan A 4f66c2c322fb

Subscribe to this mod's changes

igniter-controllers 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,335 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.