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/tools-reference)<a href="https://agentmods.dev/rules/felipebarcelospro/igniter-js/tools-reference"><img src="https://agentmods.dev/badge/rules/felipebarcelospro/igniter-js/tools-reference/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/tools-reference"><img src="https://agentmods.dev/badge/rules/felipebarcelospro/igniter-js/tools-reference.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.05983 | $0.05983 |
| Opus 5.5 | $0.02393 | $0.02393 |
| Sonnet 5.5 | $0.01197 | $0.01197 |
| Haiku 4.5 | $0.00598 | $0.00598 |
Grade A, and why
tools-reference 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tools Complete Reference
Tool Categories & Workflow Integration
CLI & Project Management
Core project development lifecycle and scaffolding tools.
dev - Start Igniter.js development server
- Description: Starts the development server, enabling live reloading, client generation, and interactive debugging.
- Parameters:
port?: number,watch?: boolean - Use when: Beginning development sessions to run the project locally and test changes in real-time.
- Workflow: Start of Work phase.
- Example:
dev({ port: 3000, watch: true })
build - Build the Igniter.js project
- Description: Compiles the project for production, including the web framework and the final Igniter.js client.
- Parameters:
mode?: "development" | "production" - Use when: Preparing for deployment or testing the production build locally.
- Workflow: Pre-deployment validation.
- Example:
build({ mode: "production" })
test - Run project test suite
- Description: Executes the project's test suite to validate changes and prevent regressions.
- Parameters:
filter?: string,watch?: boolean - Use when: After making changes to ensure code quality and correctness.
- Workflow: Work phase validation, continuous testing.
- Example:
test({ filter: "@igniter-js/core", watch: false })
generateFeature - Scaffold a new feature module
- Description: Creates a new, fully structured feature module with directories for controllers, procedures, and types.
- Parameters:
name: string,schema?: string - Use when: Starting a new area of functionality (e.g., 'users', 'products').
- Workflow: Planning and initial Work phase.
- Example:
generateFeature({ name: "user-management" })
generateController - Scaffold a new controller
- Description: Creates a new controller file within an existing feature to group related API actions.
- Parameters:
name: string,feature: string - Use when: Adding a new set of related endpoints to a feature (e.g., a 'profile' controller in the 'user' feature).
- Workflow: Work phase, when expanding a feature.
- Example:
generateController({ name: "profile", feature: "user" })
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 · 410 lines · 5,983 tokens per session scan A 89207034c1cc
tools-reference is a cursor rule published in the GitHub repository felipebarcelospro/igniter-js (241 stars, last pushed 8d ago), licensed Apache-2.0. It adds 5,983 tokens to every session, about $0.0239 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.
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.
docs
Readme wording constraints, WordPress readme format, changelog prose style, and public API naming requirements.
core
Repository coding standards and conventions for AI assistants.