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 jrenaldi79/harness-engineering --skill readinessgit clone --depth 1 https://github.com/jrenaldi79/harness-engineeringWrote 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/jrenaldi79/harness-engineering/readiness)<a href="https://agentmods.dev/skills/jrenaldi79/harness-engineering/readiness"><img src="https://agentmods.dev/badge/skills/jrenaldi79/harness-engineering/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/jrenaldi79/harness-engineering/readiness"><img src="https://agentmods.dev/badge/skills/jrenaldi79/harness-engineering/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.00062 | $0.04266 |
| Opus 5.5 | $0.00025 | $0.01706 |
| Sonnet 5.5 | $0.00012 | $0.00853 |
| Haiku 4.5 | $0.00006 | $0.00427 |
Grade B, and why
readiness scanned grade B with 2 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 1mo 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
SKILL_DIR=$(find ~/.claude/plugins -path "*/readiness/SKILL.md" -print -quit | xargs dirname) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- [ ] Deny list blocks destructive operations (rm -rf /, git push --force, git reset --hard, etc.) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource Resolution Preamble
Before any other step, resolve both the readiness skill's directory and the setup skill's resources:
SKILL_DIR=$(find ~/.claude/plugins -path "*/readiness/SKILL.md" -print -quit | xargs dirname)
SETUP_SKILL_DIR=$(find ~/.claude/plugins -path "*/setup/SKILL.md" -print -quit | xargs dirname)
SETUP_SCRIPTS=$SETUP_SKILL_DIR/scripts
SETUP_TEMPLATES=$SETUP_SKILL_DIR/templates
SETUP_REFERENCES=$SETUP_SKILL_DIR/references
If SKILL_DIR is empty, halt and tell the user: "Could not locate the readiness plugin directory under ~/.claude/plugins. Verify the plugin is installed."
If SETUP_SKILL_DIR is empty, halt and tell the user: "Could not locate the setup plugin directory. The readiness skill requires the setup skill to be installed as part of the same plugin."
The setup skill's files are references only — read them to understand what good enforcement looks like, but never blindly run install scripts on an existing project.
Phase 1: Detect Environment & Load Previous Report
Check the working directory for:
Manifest files: package.json, pyproject.toml, go.mod, Cargo.toml, CMakeLists.txt, Makefile
Git: .git/ exists
Existing agent config: CLAUDE.md, AGENTS.md, .claude/, .cursor/
Stack detection: Infer language, framework, and package manager from manifest contents.
Monorepo detection: Check for:
package.json→workspacesfieldpnpm-workspace.yamlCargo.toml→[workspace]- Go workspace (
go.work) - Lerna (
lerna.json), Nx (nx.json), Turborepo (turbo.json)
If monorepo: identify each app/package as a separate scoring unit.
Previous report: Check for readiness-report.md. If present, read the YAML frontmatter to enable delta comparison at the end.
Phase 2: Parallel Subagent Evaluation
Use subagents to keep the main context clean. Each subagent receives:
- The specific reference file paths it needs (resolved from the preamble)
- The project path to evaluate
- The stack info detected in Phase 1
- Its pillar criteria to evaluate (from Phase 3 below)
- Whether this is a monorepo and if so, the list of app/package paths
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.
- 1mo ago First seen · 334 lines · 62 tokens per session scan B 306e4a9820f6
readiness is a skill published in the GitHub repository jrenaldi79/harness-engineering (123 stars, last pushed 9d ago), licensed MIT. It adds 62 tokens to every session and 4,266 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agentic-code-review
Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.
intelligence-review-skills
Audit the intelligence layer for duplication, drift, size, hardcoded paths and framing.
independent-review
Review a batch of changes as an independent reviewer who did not write them, before commit or push. Use after a set of edits, after an autonomous loop, or when the user asks for a pre-commit review.
safe-change
Trace, implement, test, and independently review one bounded software change. Use for ordinary feature, bug-fix, or refactor work after the repository is bootstrapped; do not use for broad repository cleanup, production operations, or undefined rewrites.
nv-context
Set up state-of-the-art context engineering for any repository. Analyzes codebase, generates multi-level CLAUDE.md/AGENTS.md hierarchy, hooks, session management, and token budgets. Based on 200+ sources including ETH Zurich, Anthropic, Google DeepMind, and Manus production data. For engineers who ship with AI agents.