loop-readiness

loop-readiness is a skill for Claude Code from thaitype/chief. It costs 87 tokens per session (1,688 once invoked), scanned A, original, MIT.

A review method for checking whether a plan is ready for an unattended loop: an agent or process that repeats without a person checking every step. It examines how the loop receives instructions and how its results will be verified.

In plain words
What is it for?
Use it to review plans for autopilots, scheduled jobs, long-running agents, and other repeated workflows before they run without human supervision.
Why use it?
It reveals missing guidance and safety checks before an autonomous workflow is allowed to run repeatedly.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the chief-skills plugin — 15 skills shipped together

Good fit Use it to review plans for autopilots, scheduled jobs, long-running agents, and other repeated workflows before they run without human supervision.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thaitype/chief/loop-readiness
Install

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.

Any agent
npx skills add thaitype/chief --skill loop-readiness
Clone the repo
git clone --depth 1 https://github.com/thaitype/chief

Made for: Claude Code.

Or install chief-skills, the plugin that ships this one along with the rest of its 15 skills.

Wrote 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.

agentmods badge for loop-readiness

README.md
[![agentmods](https://agentmods.dev/badge/skills/thaitype/chief/loop-readiness/github.svg)](https://agentmods.dev/skills/thaitype/chief/loop-readiness)
Your own site
<a href="https://agentmods.dev/skills/thaitype/chief/loop-readiness"><img src="https://agentmods.dev/badge/skills/thaitype/chief/loop-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.

agentmods 80×15 button for loop-readiness

Your own site · 80×15
<a href="https://agentmods.dev/skills/thaitype/chief/loop-readiness"><img src="https://agentmods.dev/badge/skills/thaitype/chief/loop-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,688 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.01688
Opus 5.5 $0.00035 $0.00675
Sonnet 5.5 $0.00017 $0.00338
Haiku 4.5 $0.00009 $0.00169

Measured 1mo ago against content hash 90600e9fd58f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

loop-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 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.

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.

skills/engineering/loop-readiness/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Loop readiness review

This is a readiness review, not a gate. It never produces a pass/fail verdict or a single overall score — it reports what's present, what's missing, and what to consider per dimension, so the person deciding whether to start the loop has the full picture.

A "loop" here means any agent/process that runs multiple iterations with no human checking every step — an autopilot, a scheduled job, a long-running agent workflow, or anything similar. The review looks at the plan for that loop, not the loop itself — nothing gets executed during this review.

Step 1: Get the plan

  • If a plan was given — as text or a file path — use it.
  • If not, use the grill-design skill if available. Otherwise, interview the user one question at a time to build up an understanding of the plan — what it's trying to do, and how it's supposed to know if it's working. One question per turn, never ask a compound question.

Step 2: Review each dimension

Walk through all four. For each, note what's present, what's missing, and how deep the coverage is — there's no fixed checklist to fill in mechanically; use judgment about how much depth this specific loop actually needs.

2.1 Definition of Ready (DoR)

Is there something written down that defines what this loop is for and where its edges are? Depending on the loop, this could include: a goal statement, explicit non-goals / out-of-scope items, a contract (data shapes, API boundaries), a UI mock or diagram — go as deep as makes sense for the stakes involved. A one-line goal can be enough for a small loop; a loop that touches production data probably needs more.

2.2 Feedforward

Feedforward is guidance given to the loop before or during each iteration, to raise the odds it does the right thing in the first place — conventions docs, skills, contracts, bootstrap scripts, code-mod tooling, anything the loop reads or is constrained by while acting. Note whether this guidance is:

  • Computational — a deterministic tool/script/generator it must go through
  • Inferential — a doc/skill it reads and applies judgment to
  • Both, or neither

Read the full file on GitHub · 131 lines

Changes

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.

  1. 1mo ago Changed · +9 lines 90600e9fd58f
  2. 2mo ago First seen · 122 lines · 87 tokens per session scan A f584fdb864db

Subscribe to this mod's changes

loop-readiness is a skill published in the GitHub repository thaitype/chief (68 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 1,688 once invoked, about $0.0003 per session on Opus 5.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-03.

Related

loop-readiness compared with skills from other repositories

loop-readiness next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
loop-readinessthaitype/chiefSkill681mo agoMITA87Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code