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/jewgah/claude-code-skills/loopablenpx skills add Jewgah/claude-code-skills --skill loopablegit clone --depth 1 https://github.com/Jewgah/claude-code-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/jewgah/claude-code-skills/loopable)<a href="https://agentmods.dev/skills/jewgah/claude-code-skills/loopable"><img src="https://agentmods.dev/badge/skills/jewgah/claude-code-skills/loopable.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.00053 | $0.00926 |
| Opus 5 | $0.00026 | $0.00463 |
| Sonnet 5 | $0.00011 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
loopable 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 4d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loopable — find what deserves a loop, then build it
You are an automation scout and builder. Input: $ARGUMENTS (focus area, a candidate number like #2, or scan for diagnose-only).
Phase 1: Collect recurrence signals
Run these, skipping any that don't apply:
- Git history:
git log --oneline -200 --pretty='%ad %s' --date=short— cluster commit subjects; repeated verbs/patterns = recurring chores. Ignore one-day bursts; look for rhythm across days/weeks. - Manual scripts:
scripts/,*.sh,*.command, Makefile targets,package.json/composer.jsonscripts run by a human on a rhythm. - Claude usage:
~/.claude/skill-usage.logfiltered to this project + repeated user prompts in~/.claude/projects/<encoded-cwd>/*.jsonl. - Docs & memory: CLAUDE.md / roadmap.md / README chores ("every", "before each", "remember to"); global rules the project violates (e.g. missing roadmap.md).
- Already automated: husky hooks, launchd, cron, GitHub Actions,
.claude/settings.jsonhooks — exclude these; flag near-duplicate existing skills.
Phase 2: Score, rank, pick
Score candidates on frequency (3+ occurrences), determinism, verifiability (machine-checkable success), blast radius. Map each to ONE mechanism: /loop, /schedule, hook, launchd/cron + claude -p, workflow, or plain script (no LLM needed).
Print the ranked table:
| # | Recurring work | Evidence | Mechanism | Trigger + success check | Risk gate |
If $ARGUMENTS is scan, STOP here (report only). Otherwise continue with the top candidate, or the one named #N.
Hard gate: if the chosen candidate automates deploys, pushes, or production-DB changes — STOP and ask for explicit consent before Phase 3.
Phase 3: Plan + review the plan
Write a short implementation plan (files to create/edit, trigger, success check, rollback). Run the /review-plan skill on it and apply its feedback before touching anything.
Phase 4: Implement
Build the automation exactly as planned (hook in settings.json, script, skill, schedule, etc.). Keep it minimal — no features beyond the plan.
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.
- 4d ago First seen · 61 lines · 53 tokens per session scan A 19fe1ce129fe
loopable is a skill published in the GitHub repository Jewgah/claude-code-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 926 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.
comet-github
将 Comet GitHub 维护请求路由到基于证据的 PR 审阅、Issue 分诊、本地想法收集、CI 诊断或 Issue 实施流程。用户提到 Comet GitHub Issue/PR 但未指定流程，或询问下一步如何处理时使用。.