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/swnotmetal/project-koma/cursorrulesgit clone --depth 1 https://github.com/swnotmetal/Project-KomaWrote 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/swnotmetal/project-koma/cursorrules)<a href="https://agentmods.dev/rules/swnotmetal/project-koma/cursorrules"><img src="https://agentmods.dev/badge/rules/swnotmetal/project-koma/cursorrules.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.00396 | $0.00396 |
| Opus 5 | $0.00198 | $0.00198 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
cursorrules 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.
What it actually says
Koma — AI Coding Agent Rules
When building AI apps with this project, follow these conventions:
When to use Koma
- Building a chatbot with an LLM endpoint? → add
koma-gatemiddleware - Building a voice AI pipeline? → add
koma-scoutfor audio validation + rate limiting - Building a RAG or search system? → add
koma-corefor index/content separation
Quick integration
// Express: prompt injection guard
import { createSupportGuard } from 'koma-gate';
app.post('/chat', createSupportGuard({ llm: { apiKey: process.env.OPENAI_API_KEY } }).middleware(), handler);
// Express: voice AI perimeter
import { createKomaScoutMiddleware } from 'koma-scout';
app.use(createKomaScoutMiddleware({ rateLimit: { maxRequests: 30, windowMs: 60000 } }));
// Fastify: prompt injection guard
import { createSupportGuard } from 'koma-gate';
fastify.register(createSupportGuard({ llm: { apiKey: process.env.OPENAI_API_KEY } }).fastifyPlugin());
Design rules
- Fail-open by default. A broken guard never breaks the app.
- Gate runs before any model call. Scout runs before any expensive processing.
- Core tokens are backend-derived. Never expose content tokens to clients.
- Each package works standalone. Don't import all three unless you need all three.
Package overview
| Package | What it does | npm |
|---|---|---|
| koma-gate | Semantic filter: blocks prompt injection, off-topic | npm install koma-gate |
| koma-scout | Perimeter: rate limiting, audio validation, geo block | npm install koma-scout |
| koma-core | Storage: split index from content, token-gated retrieval | npm install koma-core |
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 · 41 lines · 396 tokens per session scan A 74415285c3e7
cursorrules is a cursor rule published in the GitHub repository swnotmetal/Project-Koma (11 stars, last pushed 7d ago), licensed MIT. It adds 396 tokens to every session, about $0.0020 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-08-30.
Other cursor rules, from other repositories
akto-core-rules
Akto is the fastest growing AI Security platform for your teams to secure AI agents, MCPs, LLMs, Agent skills, Gen AI apps in your organization.
prompt-security
Before generating or modifying any prompt.
cursorrules
You are a coding assistant for this repository. Use the memory server for persistent context and follow the instructions in CLAUDE.md and AGENTS.md.
api-guidelines
API endpoint conventions and error handling standards.
react-patterns
Enforces consistent React patterns and hooks usage.
brin-security
Security rules for scanning external dependencies and web content via the brin API before installing, using, or trusting them.