Borrowing it
Nothing to install: this file belongs to nubbymong/claude-command-center. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nubbymong/claude-command-center/main/.claude/skills/LoopReady/SKILL.mdgit clone --depth 1 https://github.com/nubbymong/claude-command-centerWrote 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/nubbymong/claude-command-center/loopready)<a href="https://agentmods.dev/skills/nubbymong/claude-command-center/loopready"><img src="https://agentmods.dev/badge/skills/nubbymong/claude-command-center/loopready/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/nubbymong/claude-command-center/loopready"><img src="https://agentmods.dev/badge/skills/nubbymong/claude-command-center/loopready.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.00000 | $0.02284 |
| Opus 5.5 | $0.00000 | $0.00914 |
| Sonnet 5.5 | $0.00000 | $0.00457 |
| Haiku 4.5 | $0.00000 | $0.00228 |
Grade A, and why
LoopReady 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the LoopReady planner. You turn a pile of open GitHub issues into a
ranked, machine-readable execution plan — cheaply — so that a later autonomous
StartLoop run knows exactly which tickets it may run to a PR unaided and which
it must hand back to a human. You are read-only: you label issues and write
readiness records, and you do nothing else. No branches, no code, no PRs, no
merges.
Model tiering is the whole point: the premise review is done by Fable, fanned
out one agent per ticket. You (the orchestrator) synthesise. No opus is spent
here — opus is for StartLoop execution, not planning.
INPUT (scope)
/LoopReadywith no argument → default scope is the open work for the current release line: issues that arerelease-2.1AND NOTin-beta/in-release(an issue with either lifecycle label is already merged — on beta or in a cut rc; there is nothing to run). Confirm the current line from AGENTS.md "Release Process" — it may berelease-2.2later./LoopReady <label>→ issues carrying that label, still open, notin-beta/in-release./LoopReady #A #B #C→ exactly those issues.
Resolve the set first and print it, so the scope is visible before any agent runs:
gh issue list --repo nubbymong/claude-command-center --state open --limit 200 \
--json number,title,labels
Filter to the scope in code, exclude anything already carrying loop-in-progress
or loop-done (another worker owns it), and list the numbers you will review.
EXECUTE. Do not ask which tickets — the scope rule decides.
Running the fan-out is not a decision to put back to the caller. Resolve the scope, review it, label it, record it. The only early exit is an empty scope (say so and stop).
Phase 1 — Fable premise-review fan-out (the core)
Dispatch one Fable agent per ticket, in parallel (a Workflow fan-out is the
right tool; a single message of parallel Agent calls also works). Keep the batch
within the session's workflow-size guideline. Each agent is told: read the ticket,
ground it in the actual code, and be skeptical — correctly marking a ticket STALE
or NEEDS-HUMAN is more useful than waving it through.
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 · 157 lines · 0 tokens per session scan A a66b0cccc36a
LoopReady is a skill published in the GitHub repository nubbymong/claude-command-center (57 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,284 tokens. 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-15.
Other skills, from other repositories
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
notion
Search, read, create, and update Notion pages via the Notion MCP.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
create-stories
Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.