Install
$ agentstack add skill-kunalsuri-ai-fication-kit-review-agent-config ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Run the review-agent-config diagnostic. Read-only. Produce a structured findings report; do NOT edit any file.
Inputs — read these files (and only these)
CLAUDE.md(project root) — full readAGENTS.md(project root) — full readpackage.json(project root) — grep for"build"and"test"script keys onlypom.xml(project root, if present) — grep `` section onlyai/guide/MODULE_MAP.md— check existence on disk; no deep read neededai/INDEX.md— check existence on disk; no deep read needed- Any
ai/guide/*.mdpaths referenced in the knowledge-map sections — existence
check only via Glob
Checks
Section A — CLAUDE.md structure
| ID | Check | Severity | |----|-------|----------| | C1 | Contains the literal @AGENTS.md directive (not just a comment or a markdown link [AGENTS.md](AGENTS.md)) | ❌ | | C2 | Has a "Hard rules" or equivalent section | ❌ | | C3 | Has a "Where to look" or knowledge-map section with explicit pointers into ai/guide/ | ❌ | | C4 | Has a token-discipline or subagent-delegation section | ⚠️ | | C5 | No unfilled placeholders: regex `, bare TODO, or the literal string fill in | ❌ | | C6 | Build command is present and not a placeholder | ❌ | | C7 | Test command is present and not a placeholder | ❌ | | C8 | Test locations are filled in (not or equivalent) | ❌ | | C9 | No reference to CLAUDEbkp*.md` files framed as active guidance (stale post-cold-start) | ⚠️ | | C10 | No Claude-specific directives duplicated wholesale from AGENTS.md | ⚠️ |
Section B — AGENTS.md structure
| ID | Check | Severity | |----|-------|----------| | A1 | Contains no Claude Code-specific directives (@import, memory syntax, hook syntax) | ⚠️ | | A2 | Hard rule present: frozen upstream / don't touch inherited code | ❌ | | A3 | Hard rule present: test before done — with actual build and test commands | ❌ | | A4 | Hard rule present: surgical diffs | ❌ | | A5 | Hard rule present: provenance tagging ([inferred] / [verified]) | ❌ | | A6 | Hard rule present: no phantom bugs / config churn | ❌ | | A7 | Hard rule present: verify claims before declaring done | ❌ | | A8 | Hard rule present: license-header matching for new files | ⚠️ | | A9 | Has a knowledge-map section pointing to ai/guide/ | ❌ | | A10 | No unfilled placeholders (same regex as C5) | ❌ | | A11 | No reference to AGENTS_bkp_*.md files framed as active guidance | ⚠️ |
Section C — Cross-file consistency
| ID | Check | Severity | |----|-------|----------| | X1 | Build command in CLAUDE.md matches build command in AGENTS.md | ❌ | | X2 | Test command in CLAUDE.md matches test command in AGENTS.md | ❌ | | X3 | Build/test commands match what package.json scripts or pom.xml actually define | ⚠️ | | X4 | At least one ai/guide/ path mentioned in any knowledge-map section resolves on disk | ❌ | | X5 | No rule in CLAUDE.md directly contradicts a rule in AGENTS.md | ❌ | | X6 | "Repo intelligence" / ai-layer description is not copy-pasted verbatim into both files | ⚠️ |
Output format
Emit the report directly to the user (do NOT write a file). Use this structure exactly:
review-agent-config — findings
══════════════════════════════════════════════════
CLAUDE.md
─────────
✅/⚠️/❌
→ ← omit this line for ✅
AGENTS.md
─────────
✅/⚠️/❌
→
Cross-file
──────────
✅/⚠️/❌
→
Summary
───────
X passed · Y warnings · Z errors
Next step:
Reporting discipline
- Report every check, not just failures. Passing checks build confidence.
- For every ❌ or ⚠️, always include a concrete one-line fix — never just
"this is wrong." Name the exact line or section to change.
- The "Next step" must name only the single highest-priority action. Do not
list all failures again.
- Severity governs the icon only; a ⚠️ warning is still reported and still
gets a fix suggestion.
What this skill does NOT do
- Does not auto-edit CLAUDE.md or AGENTS.md.
- Does not check
ai/guide/content quality — that is/post-cold-start-verification. - Does not assess overall AI-layer maturity — that is
/verify-ai-readiness. - Does not run builds or tests.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kunalsuri
- Source: kunalsuri/ai-fication-kit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.