Borrowing it
Nothing to install: this file belongs to c9r-io/orchestrator. 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/c9r-io/orchestrator/main/.claude/skills/project-readiness/SKILL.mdgit clone --depth 1 https://github.com/c9r-io/orchestratorWrote 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/c9r-io/orchestrator/project-readiness)<a href="https://agentmods.dev/skills/c9r-io/orchestrator/project-readiness"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/project-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/skills/c9r-io/orchestrator/project-readiness"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/project-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.00040 | $0.00463 |
| Opus 5 | $0.00020 | $0.00231 |
| Sonnet 5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
project-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 9d 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.
What it actually says
Project Readiness
Produce a revision-pinned, evidence-backed readiness verdict. A missing deployment surface is not applicable, not an implicit pass and not permission to synthesize infrastructure.
Agent Orchestrator Baseline
-
Record revision and worktree state with
git rev-parse HEADandgit status --short. -
Run the local readiness helper:
.claude/skills/project-readiness/scripts/check_local.sh -
Verify the Rust workspace with the repository's required commands: formatting check, workspace tests, and Clippy with warnings denied.
-
Verify the Web UI from
gui/with the scripts declared ingui/package.json; include build and tests, and E2E when UI behavior is in scope. -
Run
scripts/qa-doc-lint.shso documentation and governance contracts are included. -
Inspect the latest relevant GitHub Actions run with
gh, and reconcile its required gates with the pinned local revision.
The helper does not reset data, start a daemon, or contact a cluster. State-changing smoke checks require explicit scope.
Optional Generated-Project Checks
If the target repository contains docker/docker-compose.yml, scripts/reset-docker.sh, k8s/base/, or deploy/, verify those exact surfaces. These are project-bootstrap outputs and are absent from the Agent Orchestrator repository.
- Compose: render config, start only when authorized, check declared health state, and capture bounded logs.
- Kubernetes: prefer offline kustomize/render checks before any cluster action.
- Deployment scripts: inspect supported dry-run behavior before execution.
Verdict
Report PASS, FAIL, or NOT APPLICABLE for:
- revision/worktree
- Rust format, tests, and lint
- Web UI tests and build
- governance docs/gates
- GitHub Actions
- runtime smoke checks
- container/Kubernetes surfaces
For every failure, include the exact command, exit code, smallest useful error excerpt, and rerun command.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 47 lines · 40 tokens per session scan A 43ca2abf1e84
project-readiness is a skill published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 463 once invoked, about $0.0002 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-30.
Other skills, from other repositories
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
cw-orient
Use at the start of any Codewhale work session, or when unsure which checkout, branch, or worktree is authoritative: establish live repo truth before reading a plan or editing a file.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.