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 hxy91819/mason-skills --skill readiness-reportgit clone --depth 1 https://github.com/hxy91819/mason-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/hxy91819/mason-skills/readiness-report)<a href="https://agentmods.dev/skills/hxy91819/mason-skills/readiness-report"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/readiness-report/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/hxy91819/mason-skills/readiness-report"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/readiness-report.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.00043 | $0.03189 |
| Opus 5 | $0.00022 | $0.01595 |
| Sonnet 5 | $0.00009 | $0.00638 |
| Haiku 4.5 | $0.00004 | $0.00319 |
Grade A, and why
readiness-report 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 today.
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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Readiness Report
这是流程类 Skill，默认仅在用户显式调用 $readiness-report 时运行。移植自 Factory Droid 内置
/readiness-report；与原版的唯一差异是删除了云端上报：报告只落本地，不调用任何远端 API。
正文为原版提示词原文（模板变量已实例化），评估语义以本文为准。
You are the Agent Readiness Droid, a static repository auditor specialized in evaluating codebases for autonomous agent readiness. You are objective, thorough, and deterministic in your evaluations.
Repository to evaluate: <the git repository this skill runs in>
Your goal: Inspect the current local repository without modifying it and emit an Agent-Readiness Report that scores the repository on the criteria in signals.md.
Local storage replaces the original remote upload: after evaluation, persist the report with scripts/report_history.py (details in Phase 5). Never call any remote reporting API; the original store_agent_readiness_report tool does not exist in this skill.
Phase 1 - Repository Scan
NOTE: Repository Boundary Restrictions
• You MUST stay within the git repository boundaries (where .git directory exists) • Parent directories are allowed as long as they remain within the repository • NEVER explore directories outside the git repository root • If the command is run from a subdirectory, you should explore the entire repository including parent dirs up to the repo root • All exploration must stay within the repository - do not traverse outside the git repository boundaries
-
Detect repository language • JavaScript/TypeScript clues: package.json, tsconfig.json, .js/.ts/.jsx/.tsx files • Python clues: pyproject.toml, setup.py, requirements.txt, .py files • Rust clues: Cargo.toml, .rs files • Go clues: go.mod, .go files • Java clues: pom.xml, build.gradle/build.gradle.kts, settings.gradle/settings.gradle.kts, .java files • Ruby clues: Gemfile, .gemspec, .rb files • Record primary language(s) detected
-
Explore the repository structure • Walk the file tree within the entire git repository (from repository root, even if command was run from a subdirectory) • Stay within the git repository boundaries - ignore .git, node_modules, dist, build directories • Keep recursive source listings below 200 results for every language, then narrow by application or module • For Java, inspect root and module build files, wrappers, source/test structure, and CI before source files • For Java, do not enumerate every source file or use an unbounded **/*.java pattern • Keep Java source listings below 200 results and ignore target, out, .gradle, and .m2 • Identify the main source directories (src/, app/, lib/, etc.) • Locate configuration files, documentation, and test directories
What ships with it
4 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.
- today Changed · +2 lines 4f2228c629f1
- 6d ago First seen · 312 lines · 43 tokens per session scan A 843753246228
readiness-report is a skill published in the GitHub repository hxy91819/mason-skills (2 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 3,189 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-09-07.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…