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/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/check-drift)<a href="https://agentmods.dev/rules/kunalsuri/ai-fication-kit/check-drift"><img src="https://agentmods.dev/badge/rules/kunalsuri/ai-fication-kit/check-drift/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/kunalsuri/ai-fication-kit/check-drift"><img src="https://agentmods.dev/badge/rules/kunalsuri/ai-fication-kit/check-drift.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.00018 | $0.00220 |
| Opus 5.5 | $0.00007 | $0.00088 |
| Sonnet 5.5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
check-drift 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.
What it actually says
Run the mechanical verification and drift analysis to inspect the state of the ai/ knowledge-base:
- Run the path verifier:
node install.mjs verify . --strict - Run the drift detector with git history comparison:
node install.mjs drift . --git --strict - Run
git statusto inspect modified and untracked files.
If any issues are reported, or if git status reveals newly added or modified source files/templates that are not yet covered in the maps:
- Draft updates to
ai/guide/MODULE_MAP.mdorai/guide/FEATURE_MAP.mdto map new folders, files, or features, or to update stale verified dates. - Mark any changes you draft as
[inferred]. - Report findings to the user and outline what needs their manual review.
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 · 19 lines · 18 tokens per session scan A 49a6442ca01c
check-drift is a cursor rule published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 12d ago), licensed Apache-2.0. It adds 18 tokens to every session and 220 once invoked, about $0.0001 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-08-31.
Other cursor rules, from other repositories
full-output-enforcement
Yapay zeka asistanının kod üretimi ve açıklamalarında hiçbir zaman kısaltma, atlama veya eksik bilgi vermemesini sağlayan meta-yetenek. "Geri kalanı aynı", "..." gibi tembel çıktıları engeller.
caveman-help
Display this reference card when invoked. One-shot — do NOT change mode, write flag files, or persist anything. Output in caveman style.
03-tool-usage
Efficient tool usage patterns for navigating and editing this repository.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.