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 agentmods add skills/openhands/extensions/improve-agent-readinessnpx skills add OpenHands/extensions --skill improve-agent-readinessgit clone --depth 1 https://github.com/OpenHands/extensionsWhat 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 | $0.00060 | $0.01480 |
| Opus 5 | $0.00030 | $0.00740 |
| Sonnet 5 | $0.00012 | $0.00296 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
improve-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 2d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Onboarding
Take a readiness report and turn its gaps into concrete, repo-appropriate fixes.
Prerequisites
This skill expects an agent readiness report to already exist — either from
running agent-readiness-report on this repo or provided by the user. If no report
exists, run the readiness report skill first.
How to run
Step 1: Read the report
Identify every ✗ (missing) feature across all five pillars.
Step 2: Propose high-impact fixes
Don't try to fix everything. Pick the 5–10 changes that would help agents the most across all pillars, ranked by impact. Not every pillar needs to be represented — focus on what matters most for this repo. The goal is to meaningfully improve the score, not to hit 74/74.
Ranking heuristic — rank by how directly the change helps an agent complete a coding task in this repo:
- Things that unblock agents from working at all (AGENTS.md, build commands, bootstrap scripts, dev environment setup)
- Things that give agents faster feedback on their work (pre-commit hooks, test documentation, PR templates with checklists)
- Things that improve quality or process (CI caching, label automation, spell checking, merge queues)
- Things that improve governance or compliance (SECURITY.md, CODEOWNERS, actionlint, CodeQL)
A single change that lets an agent build and test the project outranks a 2-for-1 that addresses minor gaps.
Proposals should fit this specific repo:
- Look at the languages, frameworks, and tools already in use
- Look at the project structure (monorepo vs single package, etc.)
- Look at what's already partially in place (don't reinvent what exists)
- Propose additions that match the repo's existing conventions and style
For each proposal, include:
- What to add or change
- Where it goes (file path)
- Which pillar(s) it improves
- Why it's high impact — use the feature descriptions in
references/criteria.mdto explain what goes wrong for agents without this feature. Don't just say "improves Agent Instructions" — say what the agent can't do today and what it'll be able to do after the fix.
What ships with it
2 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.
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.
- 2d ago First seen · 168 lines · 60 tokens per session scan A e34bcd869080
improve-agent-readiness is a skill published in the GitHub repository OpenHands/extensions (137 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 1,480 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…