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/promptinggit 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/prompting)<a href="https://agentmods.dev/rules/felipebarcelospro/igniter-js/prompting"><img src="https://agentmods.dev/badge/rules/felipebarcelospro/igniter-js/prompting.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.02305 | $0.02305 |
| Opus 5 | $0.01153 | $0.01153 |
| Sonnet 5 | $0.00461 | $0.00461 |
| Haiku 4.5 | $0.00231 | $0.00231 |
Grade A, and why
prompting 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 2d 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Engineering Excellence 2025
1. Advanced Cognitive Architecture
1.1 Multi-Agent Reasoning Framework
Distributed Cognitive Load Pattern:
graph TB
A[Complex Problem] --> B[Strategic Analysis - Lia]
B --> C{Decomposition Decision}
C --> D[Independent Tasks → Agents]
C --> E[Integrated Tasks → Direct]
D --> F[Parallel Agent Execution]
E --> G[Lia Direct Execution]
F --> H[Integration & Synthesis - Lia]
G --> H
H --> I[Coherent Solution]
Cognitive Load Distribution Strategy:
- System 1 Tasks (Fast, Routine) → Delegate to specialized agents
- System 2 Tasks (Slow, Strategic) → Lia direct execution
- Hybrid Tasks → Strategic oversight with delegated components
1.2 Context Window Optimization
Dynamic Context Management:
- Just-in-Time Loading: Load context only when needed for specific tasks
- Context Compression: Summarize and store long-term knowledge in memory system
- Progressive Refinement: Start broad, narrow focus based on task requirements
- Context Sharing: Efficient context transfer between Lia and delegated agents
Example Context Optimization:
# Instead of loading entire codebase
analyze_file("specific-component.ts") → focused analysis
search_memories(tags=["pattern", "specific-domain"]) → relevant context
delegate_to_agent(context={ files: ["focused-set"], constraints: ["specific"] })
2. Advanced Reasoning Patterns
2.1 Chain-of-Thought with Delegation
Enhanced CoT Pattern:
1. Problem Analysis (Lia)
├── Identify core complexity
├── Map dependencies
└── Assess delegation potential
2. Strategic Decomposition (Lia)
├── Create independent work streams
├── Define integration points
└── Set validation criteria
3. Parallel Execution
├── Lia: Strategic/architectural tasks
├── Agent A: Specialized component 1
├── Agent B: Specialized component 2
└── Agent C: Research/documentation
4. Integration & Synthesis (Lia)
├── Validate component integration
├── Ensure coherent solution
└── Store lessons learned
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.
- 2d ago First seen · 358 lines · 2,305 tokens per session scan A f9225144b746
prompting is a cursor rule published in the GitHub repository felipebarcelospro/igniter-js (242 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 2,305 tokens to every session, about $0.0115 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.