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/baek-labs/hames/readynpx skills add baek-labs/hames --skill readygit clone --depth 1 https://github.com/baek-labs/hamesWrote 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/baek-labs/hames/ready)<a href="https://agentmods.dev/skills/baek-labs/hames/ready"><img src="https://agentmods.dev/badge/skills/baek-labs/hames/ready.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00266 |
| Opus 5 | $0.00008 | $0.00133 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
ready 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.
What it actually says
Ready
Turn the user's intent into a reviewable Hames contract. Do not start execution.
Read .hames/config.yaml, the selected workspace, and applicable project rules before drafting the contract.
Record the goal, targets, actions, allowed and denied scope, outputs, invariants, acceptance criteria, evidence, and risk without choosing implementation details for the user.
For a new document, record, web resource, or external resource, use the location and name already stated by the user. Ask only for a missing parent or planned_name; do not ask again when both are known.
Require before, action, and after evidence for external changes unless the contract records a reason and explicit exception approval. Mark critical actions; /ready approval does not authorize executing them.
Show the human-readable contract and wait for current-user approval. Only then record approval tied to the exact revision and specification hash and move the contract to READY.
Use the bundled runtime/contract.js draft, amend, and approve commands. Stage machine input only under ignored .hames/state/, include no secret values, and pass --approved only after the user approves the displayed contract.md.
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 First seen · 21 lines · 16 tokens per session scan A b939599a6137
ready is a skill published in the GitHub repository baek-labs/hames (5 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 266 once invoked, about $0.0001 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-04.
Other skills, from other repositories
代码审查员
专业代码审查专家，提供建设性、可操作的反馈，聚焦正确性、可维护性、安全性和性能，而非代码风格偏好。.
release-gate-loop
发版前自动验证闸门——V 验证 + F 修复循环（verdict FAIL → F 改代码 → 跑 audit → V 重验），最大 3 轮直到 PASS。纯只读验证 + 最小修复。.
fresh-eyes-loop
发布后独立质量循环——A/B 双盲 12 视角 fresh-eyes 审查 + 修复 + 验证，每轮新 session 保证零上下文，连续 2 轮无 P0/P1 即停。.
sofagent-fde
前线部署与知识工程专家。梳理企业业务流、识别 AI 节点、构建 ontology 本体数据、交付离场。 部署完成后转为持续优化模式（sustain），自动读 audit 报告趋势生成优化报告。 不写应用代码——把企业业务规则、组织架构、系统边界转译成 sofagent 的数据层和约束层。.
sofagent-audit
收到用户任务后，不要自己执行——用 Bash tool 把任务交给 DeepAgents 编排引擎：.
b3os-ai-code-safety
As code and logic grow, the cost is not the happy path — it is coupling: a change ripples into places you did not touch, and a "small fix" breaks something unrelated. This skill is a code-structure and refactoring guide: structure well from the initial design so a change stays local, apply operational safety where…