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/kunalsuri/ai-fication-kit/perform-feature-add-simulationgit clone --depth 1 https://github.com/kunalsuri/ai-fication-kitWrote 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/kunalsuri/ai-fication-kit/perform-feature-add-simulation)<a href="https://agentmods.dev/rules/kunalsuri/ai-fication-kit/perform-feature-add-simulation"><img src="https://agentmods.dev/badge/rules/kunalsuri/ai-fication-kit/perform-feature-add-simulation.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.1 | $0.00023 | $0.00278 |
| Opus 5 | $0.00012 | $0.00139 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
perform-feature-add-simulation 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 5d 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
Simulate adding the feature the user names — WITHOUT writing a single line of code. This is a pre-flight check of both the plan and the knowledge layer.
Phases to walk (score each: smooth / friction / blocked)
- Locate — can MODULE_MAP + FEATURE_MAP/CATALOG identify the target modules without crawling? Name them.
- Plan — draft the touch list per layer; note Stability of every file you'd
change. Any
frozenor?file ⇒ blocked pending human approval. - Verify — which suites would prove it works; do they exist and are commands confirmed?
- Knowledge update — which ai/ files would need updating after the change?
Output
A friction report in chat (and, if asked, saved to ai/analysis/audit-reports/): per-phase score with the specific missing knowledge that caused friction, total estimated context cost, and a go / no-go recommendation. Knowledge gaps found here are the cheapest bugs you will ever fix — file each as an audit TODO.
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.
- 5d ago First seen · 24 lines · 23 tokens per session scan A d4f9932ee4bb
perform-feature-add-simulation is a cursor rule published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 23 tokens to every session and 278 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
x-harness
Use only light, standard, deep. Do not use small, medium, large.
chinese-language
CRITICAL: You MUST respond in Simplified Chinese at ALL times unless explicitly requested otherwise. 回复、注释、commit message 使用简体中文。技术术语保持英文原文。.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
schema
Scalable and secure schema design patterns for relational databases, NoSQL, and APIs. / TR: İlişkisel veri tabanları, NoSQL ve API'ler için ölçeklenebilir ve güvenli şema tasarım kalıpları.
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
bash-style
Bash 核心规范：禁止行尾注释、文件写入用 tee、Heredoc 默认禁止变量展开.