An autonomous runner for a Markdown task queue, where each checked or unchecked line represents a work item. It carries tasks through planning, implementation, review, testing, documentation, committing, and pushing.

Use it with a task file or task ID to process work items one at a time, apply the repository's own rules, fix review findings, verify the result, and mark completed tasks.

It removes much of the repeated coordination needed to deliver several tasks in order, while pausing when a product decision is genuinely required.

loopit — Skill for Claude Code by Jewgah/claude-code-skills

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 Jewgah/claude-code-skills --skill loopit

Clone the repo

git clone --depth 1 https://github.com/Jewgah/claude-code-skills

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jewgah/claude-code-skills/loopit/github.svg)](https://agentmods.dev/skills/jewgah/claude-code-skills/loopit)

Your own site

<a href="https://agentmods.dev/skills/jewgah/claude-code-skills/loopit"><img src="https://agentmods.dev/badge/skills/jewgah/claude-code-skills/loopit/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jewgah/claude-code-skills/loopit"><img src="https://agentmods.dev/badge/skills/jewgah/claude-code-skills/loopit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 7,213 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00095	$0.07213
Opus 5.5	$0.00038	$0.02885
Sonnet 5.5	$0.00019	$0.01443
Haiku 4.5	$0.00010	$0.00721

Measured 6d ago against content hash ee185e9f0c03, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

loopit 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 6d 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/loopit/SKILL.md · 431 lines

How it starts

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

Loopit - run a task queue through the full delivery flow

You are an autonomous delivery runner, project-agnostic. Input: $ARGUMENTS - a path to a tasks file (default ./loop-tasks.md), or a single TASK-ID to run only that task.

Process tasks strictly one at a time, top to bottom, each through the complete cycle below. The loop is autonomous between tasks - do not ask "should I continue" after each one. Pause only at the explicit gates in "When to pause".

Nothing here is hardcoded to a specific project. Every project-specific rule (branch, deploy, commit style, client-doc format, post-push build) is derived from the target repo in Step 0 - primarily from its CLAUDE.md + recalled memories + its tooling files. If a repo needs a special rule, it belongs in that repo's CLAUDE.md, not in this skill.

Inputs

$ARGUMENTS empty → read ./loop-tasks.md in the current directory.
$ARGUMENTS = a path → use that tasks file.
$ARGUMENTS = a TASK-ID (e.g. FX-A03) → run only that task, then stop.

The tasks file's directory anchors any relative repo paths (below).

Tasks file format

A markdown checklist. Each line:

- [ ] TASK-ID | repo | Title - short description / acceptance / notes

[ ] = pending, [x] = done, [~] = blocked (needs a decision; skip and report).
repo = the working directory for the task. Resolve as: an absolute path as-is; a relative path against the tasks-file's directory; . or empty → the current repo. Do NOT assume any fixed parent directory.
Lines starting with # are section headers; ignore for processing.
A task line may be followed by indented grounding notes, one per line, starting with two spaces and > (attachment digests, decisions from a ticket's comments, and similar). They belong to the task above and are passed VERBATIM to that task's subagent as Extra grounding; they are not tasks.
A task tagged (decision) in its notes needs product input - see "When to pause".

Read the full file on GitHub · 431 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.

6d ago Changed ee185e9f0c03
14d ago Changed c1b844530bd6
1mo ago Changed · +205 lines · +27 tokens per session 48aa9d45478b
1mo ago First seen · 226 lines · 68 tokens per session scan A 2b9f880b7985

Subscribe to this mod's changes

loopit is a skill published in the GitHub repository Jewgah/claude-code-skills (2 stars, last pushed 6d ago), licensed MIT. It adds 95 tokens to every session and 7,213 once invoked, about $0.0004 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-08-31.

Claude Code Code review Commits Git and workflow Project management ai-agents claude skills slash-commands

antfu-create-pr

Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.

antfu/skills · 54 tokens

friction-log

File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.

educlopez/ui-craft · 52 tokens

split-and-ship

Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".

tobihagemann/turbo · 61 tokens

loopit