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 zacharygcook/agent-skills --skill agent-readinessgit clone --depth 1 https://github.com/zacharygcook/agent-skillsWrote 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/zacharygcook/agent-skills/agent-readiness)<a href="https://agentmods.dev/skills/zacharygcook/agent-skills/agent-readiness"><img src="https://agentmods.dev/badge/skills/zacharygcook/agent-skills/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/skills/zacharygcook/agent-skills/agent-readiness"><img src="https://agentmods.dev/badge/skills/zacharygcook/agent-skills/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.00081 | $0.01360 |
| Opus 5 | $0.00041 | $0.00680 |
| Sonnet 5 | $0.00016 | $0.00272 |
| Haiku 4.5 | $0.00008 | $0.00136 |
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 10d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Readiness
Produce a personally owned, vendor-neutral readiness assessment from a transparent 82-criterion rubric. Prefer real engineering capability over score theater and make every judgment auditable.
Choose the operation
- Audit-report: inspect and score without changing the repository, then generate HTML, PDF when local Chromium is available, Markdown, and JSON artifacts.
- Initialize preferences: copy
assets/DEFAULT_AGENT_READINESS_PREFERENCES.mdtoAGENT_READINESS_PREFERENCES.mdin the repository root only when the user requests it or approves repository changes. Never overwrite an existing file. - Remediate-one: score, select one failing criterion, implement a durable repo-specific fix, validate it, rescore it, and commit only that fix when authorized.
- Improve-to-target: repeat one criterion and one commit at a time until the requested owned percentage or level is reached, or a genuine blocker requires user authority.
- Compare: compare two assessments or reports and make regressions visible even when the total score rises.
For audit-report or compare, read references/rubric.json and references/report-workflow.md
completely. For remediate-one or improve-to-target, also read references/remediation-loop.md.
Apply preferences in this order: explicit instructions in the
current request, root AGENT_READINESS_PREFERENCES.md, then
assets/DEFAULT_AGENT_READINESS_PREFERENCES.md. State which file was used. Preferences guide how to
implement a capability; they are not standing permission to create or connect third-party accounts,
accept costs, install external apps, add secrets, or mutate production.
Audit workflow
- Read repository instructions and preferences before evaluating anything.
- Record the current commit and dirty-tree state. Audits are read-only.
- Discover deployable/runnable applications from source, manifests, workspace configuration, and deployment files. Libraries are applications only when independently built, tested, or shipped.
- Evaluate all 82 criteria. Repository criteria receive one judgment. Application criteria receive
one judgment per application:
pass,fail, ornot_applicable. - Use
not_applicableonly for skippable criteria and explain why that application is outside the criterion's actual risk surface. Never infer failure merely from inapplicability. - Require concrete evidence for every pass. Prefer source/config paths and successful commands; external-state criteria may cite CLI/API output. Do not award credit for prose claiming an implementation exists when the implementation is absent.
- Create an assessment matching
references/assessment-format.md. Record command and external-state checks inprovenance.evidence_checks; store concise summaries, timestamps, and exit status rather than secrets or raw output. - Add repository-aware recommendations following
references/report-workflow.md, then validate and render it with:
What ships with it
17 files 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.
- agents/openai.yaml 280 B
- assets/DEFAULT_AGENT_READINESS_PREFERENCES.md 2.6 KB
- assets/readiness-loop-dark.json 277 B
- assets/readiness-loop-dark.svg 20 KB
- assets/readiness-loop-light.json 590 B
- assets/readiness-loop.mmd 716 B
- assets/readiness-loop.svg 20 KB
- evals/scenarios.json 2.5 KB
- references/assessment-format.md 5.8 KB
- references/remediation-loop.md 3.9 KB
- references/report-workflow.md 2.6 KB
- references/rubric.json 21 KB
- scripts/agent_eval.py 8.6 KB runs code
- scripts/readiness.py 102 KB runs code
- scripts/test_agent_eval.py 3.8 KB runs code
- scripts/test_readiness.py 32 KB runs code
- VERSION 6 B
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.
- 10d ago First seen · 99 lines · 81 tokens per session scan A bc034addb86e
agent-readiness is a skill published in the GitHub repository zacharygcook/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,360 once invoked, about $0.0004 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.
Other skills, from other repositories
pptx-html-fidelity-audit
Audit a python-pptx export against its source HTML deck, identify layout/content drift (footer overflow, cropped content, missing italic/em, lost styling, off-rhythm spacing), and re-export with strict footer-rail + cursor-flow layout discipline. Use this skill whenever the user has a .pptx that was generated from an…
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
nemo-automodel-model-onboarding
Guide for onboarding new model architectures into NeMo AutoModel, including architecture discovery, implementation patterns, registration, and validation.
amc-run-sample-calibration
Run end-to-end calibration on the shipped sample dataset (sdg082sampledata010926.zip) against a running AMC microservice. Use when user says 'test sample dataset', 'run sample calibration', 'verify AMC install', or 'launch and test'.
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.