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/add-featuregit 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/add-feature)<a href="https://agentmods.dev/rules/kunalsuri/ai-fication-kit/add-feature"><img src="https://agentmods.dev/badge/rules/kunalsuri/ai-fication-kit/add-feature.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.00023 | $0.00371 |
| Opus 5 | $0.00012 | $0.00186 |
| Sonnet 5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
add-feature 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 4d 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
Implement the requested feature following the add-feature skill contract (VS Code
auto-discovers it from .claude/skills/add-feature/ or .agents/skills/add-feature/
in this repo). Summary of the contract:
- Spec first. If no spec exists in
ai/lab/specs/, draft one from the template and get the user's OK before writing code. - Locate via the maps. MODULE_MAP → FEATURE_MAP/CATALOG → WORKLOG history (was this area just changed?) → open only what's needed.
- Respect Stability. Never modify
frozenor?files without explicit human approval in this conversation. - Build surgically. Smallest diff that satisfies the spec; match conventions and license headers.
- Verify. Run the suite(s) matching the change. Failing or unrun tests ⇒ not done.
- Update knowledge. FEATURE_MAP entry, catalog amendment, MODULE_MAP if layout
changed — all tagged
[inferred]for the human to verify. - Review & record. Request
/review-changeon the diff (fresh context), then append the work's row toai/lab/WORKLOG.mdlinking spec, review, and commits, and move the feature'sai/lab/ROADMAP.mdrow from Planned to Shipped — cross-linking the spec, the WORKLOG row, and the PR by feature ID.
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.
- 4d ago First seen · 26 lines · 23 tokens per session scan A 09273991bfd9
add-feature is a cursor rule published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 371 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.
01-qa-agent
QA AGENT PERSONA: Principles, Anti-patterns, workflows.
cursorrules
ALWAYS start your session by reading AGENTS.md and .memory/wiki/hot.md to get project context before suggesting code or answering questions.
head-of-product
Head of Product persona — planning, user stories, UX decisions, scope guardian. Use when discussing product strategy, PRDs, user research, feature proposals, or backlog prioritization.
bash-style
Bash 核心规范：禁止行尾注释、文件写入用 tee、Heredoc 默认禁止变量展开.
chinese-language
CRITICAL: You MUST respond in Simplified Chinese at ALL times unless explicitly requested otherwise. 回复、注释、commit message 使用简体中文。技术术语保持英文原文。.