Borrowing it
Nothing to install: this file belongs to xsovad06/sova. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.claude/commands/agent-readiness.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/commands/xsovad06/sova/agent-readiness)<a href="https://agentmods.dev/commands/xsovad06/sova/agent-readiness"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/agent-readiness/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/commands/xsovad06/sova/agent-readiness"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/agent-readiness.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.00016 | $0.01540 |
| Opus 5.5 | $0.00006 | $0.00616 |
| Sonnet 5.5 | $0.00003 | $0.00308 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
agent-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 16d 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assess the current repository's readiness for AI-assisted development, then offer to improve it step by step. $ARGUMENTS
Whenever you need to ask the user a question, always use the AskUserQuestion tool; never ask as plain text.
When a step involves a discussion with the user, tell them they can say "done" or "skip" to move on to the next step.
Step 1. Assess (before)
Present this explanation:
This skill helps you build a layered documentation system for AI-assisted development. Each file has a distinct role:
.claude/rules/*.md: Detailed, domain-specific playbooks (security, testing, database, etc.) with concrete rules agents follow. A rule with nopathsin its frontmatter loads at launch, into every Claude Code session; a rule scoped withpathsloads only when Claude Code opens a file matching that pattern, not every sessionAGENTS.md: The onboarding doc for any AI agent: cross-cutting conventions + an index pointing to the guideline filesCLAUDE.md: A thin, Claude Code-specific layer that imports AGENTS.md and adds Claude-only behavior (build commands, etc.).coderabbit.yaml: Points CodeRabbit (AI code reviewer) to the guideline files so it enforces your conventions during PR reviewsREADME.md: The front door: high-level project context for humans and agents alikeCONTRIBUTING.md: Contribution conventions for both humans and agentsdocs/ARCHITECTURE.md: Institutional knowledge about the system's design and key architectural decisionsWe'll check what's already in place, then walk through each file step by step.
Check every requirement and present results:
| # | Requirement | How to check |
|---|---|---|
| 1 | Domain-specific guideline files (.claude/rules/*.md) |
Glob for files: pass if at least one domain file exists (for example security.md, testing.md) |
| 2 | AGENTS.md with AI-specific guidance and docs index | Check repo root |
| 3 | CLAUDE.md imports AGENTS.md (@AGENTS.md) |
Check repo root |
| 4 | CodeRabbit configured (.coderabbit.yaml) |
Check knowledge_base.code_guidelines.filePatterns includes .claude/rules/*.md |
| 5 | README.md with foundational context | Check repo root |
| 6 | CONTRIBUTING.md with contribution conventions | Check repo root |
| 7 | docs/ARCHITECTURE.md with institutional knowledge | Check for file |
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.
- 16d ago Changed · +2 lines f8459204c033
- 2mo ago First seen · 142 lines · 16 tokens per session scan A 672e8477a151
agent-readiness is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 1,540 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 commands, from other repositories
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
review
Review current changes for correctness, style, and potential issues.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
code-review-give
Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.