verify-ai-readiness

verify-ai-readiness is a cursor rule for Cursor from kunalsuri/ai-fication-kit. It costs 22 tokens per session (326 once invoked), scanned A, original, Apache-2.0.

A read-only assessment of how prepared a repository is for work by coding agents. It scores the project's instructions, knowledge maps, feature information, conventions, diagrams, and recorded evaluations on a five-level scale.

In plain words
What is it for?
Use it to produce a dated readiness report, identify the repository's maturity level, and record the single most valuable next improvement.
Why use it?
It reveals gaps that could make an agent guess about the codebase or implement changes unsafely.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Good fit Use it to produce a dated readiness report, identify the repository's maturity level, and record the single most valuable next improvement.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/kunalsuri/ai-fication-kit/verify-ai-readiness
Install

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.

Clone the repo
git clone --depth 1 https://github.com/kunalsuri/ai-fication-kit

Made for: Cursor.

Wrote 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.

agentmods badge for verify-ai-readiness

README.md
[![agentmods](https://agentmods.dev/badge/rules/kunalsuri/ai-fication-kit/verify-ai-readiness.svg)](https://agentmods.dev/rules/kunalsuri/ai-fication-kit/verify-ai-readiness)
Your own site
<a href="https://agentmods.dev/rules/kunalsuri/ai-fication-kit/verify-ai-readiness"><img src="https://agentmods.dev/badge/rules/kunalsuri/ai-fication-kit/verify-ai-readiness.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 326 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00326
Opus 5 $0.00011 $0.00163
Sonnet 5 $0.00004 $0.00065
Haiku 4.5 $0.00002 $0.00033

Measured 8d ago against content hash c0a05796b692, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

verify-ai-readiness 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 8d 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.

.cursor/rules/verify-ai-readiness.mdc · 28 lines

What it actually says

Assess how ready this repository is for agentic work. Read-only; output one report.

The maturity scale

  • Level 0 — Opaque. No agent entry files; agents crawl and guess.
  • Level 1 — Scaffolded. Kit installed; maps exist but are placeholders.
  • Level 2 — Drafted. /cold-start ran; maps populated but [inferred].
  • Level 3 — Verified. Human audit done: Stability set, core rows [verified]. The minimum bar for letting an agent build features.
  • Level 4 — Maintained. Feature catalog exists; knowledge updated on merge; audits recur; evaluations recorded in ai/lab/.

Method

Score each: entry files (CLAUDE.md/AGENTS.md), MODULE_MAP coverage & verification ratio (% rows [verified]), FEATURE_MAP/CATALOG coverage, conventions, diagrams, ai/lab/ activity. Evidence = file contents only; no speculation.

Output

Write ai/analysis/audit-reports/<YYYY-MM-DD>-readiness.md: overall level, per-area table (area · evidence · level), the SINGLE most valuable next action, and any agent-blocking gaps (anything that would make a feature build unsafe today). Tag the report [inferred].

Changes

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.

  1. 8d ago First seen · 28 lines · 22 tokens per session scan A c0a05796b692

Subscribe to this mod's changes

verify-ai-readiness is a cursor rule published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 22 tokens to every session and 326 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.