readiness-auditor

readiness-auditor is an agent for Claude Code from cembasaranoglu/crafting-system-claude. It costs 23 tokens per session (233 once invoked), scanned A, original, MIT.

A repository readiness checker that reviews whether a code project is prepared for security, release, compliance, and other listed gates, then records each result in an evidence matrix.

In plain words
What is it for?
Use it to assess a repository before release or launch, identify missing evidence, and assign each finding an impact, severity, and required action.
Why use it?
It separates verified facts from claims, assumptions, unknowns, and blocked checks. This helps prevent unsupported readiness or release decisions.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the crafting-system plugin — 81 skills, 32 agents shipped together

Good fit Use it to assess a repository before release or launch, identify missing evidence, and assign each finding an impact, severity, and required action.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/cembasaranoglu/crafting-system-claude/readiness-auditor
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/cembasaranoglu/crafting-system-claude

Made for: Claude Code.

Or install crafting-system, the plugin that ships this one along with the rest of its 81 skills, 32 agents.

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 readiness-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/cembasaranoglu/crafting-system-claude/readiness-auditor.svg)](https://agentmods.dev/agents/cembasaranoglu/crafting-system-claude/readiness-auditor)
Your own site
<a href="https://agentmods.dev/agents/cembasaranoglu/crafting-system-claude/readiness-auditor"><img src="https://agentmods.dev/badge/agents/cembasaranoglu/crafting-system-claude/readiness-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 233 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.00023 $0.00233
Opus 5 $0.00012 $0.00117
Sonnet 5 $0.00005 $0.00047
Haiku 4.5 $0.00002 $0.00023

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

Security

Grade A, and why

readiness-auditor 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.

cowork/agents/readiness-auditor.md · 20 lines

What it actually says

readiness-auditor

You are a readiness auditor. Audit repository readiness gates (security, supply chain, OSS, observability, performance, docs/DX, compliance, API, data/schema, AI-ready, MCP, release/launch) and produce a strict pass/fail/blocked evidence matrix.

Rules:

  • Inspect available source material first.
  • Do not fabricate repository state, validation status, implementation status, readiness, or release status.
  • Use exact labels: validated, source_evidenced, declared_only, assumption, unknown, blocked, not_run, not_applicable, failed.
  • When producing findings, include evidence, impact, severity, and required action.
  • Stay within the requested stage boundary.
  • For write operations, require explicit authorization unless the active user instruction already authorizes the exact operation.

Recommended companion skills: readiness-gates, security-supply-chain, oss-release-readiness.

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 · 20 lines · 23 tokens per session scan A 9ecf0e7d2696

Subscribe to this mod's changes

readiness-auditor is an agent published in the GitHub repository cembasaranoglu/crafting-system-claude (5 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 233 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.