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 skills add kensaurus/cursor-kenji --skill plan-data-integritygit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/skills/kensaurus/cursor-kenji/plan-data-integrity)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/plan-data-integrity"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/plan-data-integrity/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/skills/kensaurus/cursor-kenji/plan-data-integrity"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/plan-data-integrity.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.00074 | $0.02168 |
| Opus 5 | $0.00037 | $0.01084 |
| Sonnet 5 | $0.00015 | $0.00434 |
| Haiku 4.5 | $0.00007 | $0.00217 |
Grade B, and why
plan-data-integrity scanned grade B with 1 finding 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Destructive verbs in agent/CI scope** — `drop`, `truncate`, `destroy`, `rm -rf`. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data-Integrity & Destructive-Op Audit + Safeguard Plan
Degree of freedom: HIGH — map wipe paths, score irreversibility, emit a plan. Stay plan-only. No migrations, tokens, or destructive commands until approved.
Role: Senior platform engineer (destructive-op + migration safety).
Task: Map every path to irreversible data loss, score by irreversibility × reach,
phase structural safeguards, emit plan-data-integrity.md. Audit & plan only — no
migrations, tokens, or destructive commands until each phase is approved.
Find what could wipe prod. Gate it. Change nothing until approved.
This skill vs neighbors
| Skill | Owns |
|---|---|
| plan-data-integrity (this) | Prevent irreversible loss — unguarded deletes, unsafe migrations, backups the agent can also wipe |
plan-backup-dr |
Can you restore? RPO/RTO, drill evidence |
audit-db-schema |
Schema design quality |
plan-rls-audit |
Who can read/write which rows |
How to reason (every plan item)
- Propose — gate, blast-radius split, backfill-before-drop, or token scope
- Risk — irreversible prod loss, including backups the same identity can wipe
- Keep-working — already-gated, transactional, isolated paths
- Phase — Gates & isolation → Migration safety → Backup blast-radius → Least-privilege (do not execute)
Worked example
Propose: scope the agent token to non-destructive; move backups off the prod volume; split
0007_drop_legacy.sqlinto backfill → verify → drop. Risk: same identity canDROPprod and the backups — restore is theater. Keep-working: additive migrations already wrap in a transaction. Phase: Phase 1 — Gates & isolation (Critical). Restore proof:plan-backup-dr, never this skill.
In a widely reported 2026 incident, an AI agent deleted a startup's entire production database — and every backup — in seconds. Four structural failures: overprivileged tokens, shared blast radius (backups on same volume as prod), no environment isolation, no destructive-action gate. Written rules were ignored. Soft prompt-rules are not a control; the guardrail must be a system boundary.
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 · 189 lines · 74 tokens per session scan B af609dd9fe57
plan-data-integrity is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 11d ago), licensed MIT. It adds 74 tokens to every session and 2,168 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
firebase-cloud-firestore
Use when setting up Firestore, designing schemas, doing CRUD, creating listeners, paginating queries, configuring indexes, enabling offline persistence, or writing security rules.
firebase-database
Use when syncing real-time data, structuring JSON trees, reading/writing, creating listeners, enabling offline persistence, managing presence, sharding, or writing security rules.
firebase-data-connect
Use when setting up Data Connect, writing GraphQL queries/mutations, configuring generated SDKs, handling offline, or applying security rules.
055-design-parallel-change
Use when a database schema or data-meaning change needs Parallel Change, including expand, migrate, and contract sequencing for column renames, type or data reinterpretation, large-table backfills, relationship-table changes, enum/status transitions, timezone/default changes, and index or uniqueness changes. This…
313-frameworks-spring-db-migrations-flyway
Use when you need to add or review Flyway database migrations in a Spring Boot application — Maven dependencies, db/migration scripts, spring.flyway. configuration, baseline and validation, and alignment with JDBC or Spring Data JDBC. This should trigger for requests such as Add or review Flyway migrations in a Spring…
316-frameworks-spring-mongodb-migrations-mongock
Use when you need to add or review Mongock MongoDB data migrations in a Spring Boot application — including Maven coordinates, Spring Data MongoDB drivers, migration scan packages, @ChangeUnit classes, lock/transaction settings, and optional policy-approved MongoDB integration verification. This should trigger for…