Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. 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/hlalljie/agent-workflow-presets/main/.cursor/skills/run-task-loop/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/run-task-loop)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/run-task-loop"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/run-task-loop/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/hlalljie/agent-workflow-presets/run-task-loop"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/run-task-loop.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.00075 | $0.01578 |
| Opus 5.5 | $0.00030 | $0.00631 |
| Sonnet 5.5 | $0.00015 | $0.00316 |
| Haiku 4.5 | $0.00007 | $0.00158 |
Grade A, and why
run-task-loop 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 19d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run task loop
Goal
Finish the work with strong coverage, without owner involvement until done, blocked, or out of credible fixes.
Modes
The active mode is set by the user and tracked by workflow-mode.mdc. Read the mode file and follow it; where it conflicts with this file, the mode file wins.
- default (no mode): this file as written. Interrupt only for Stop only for items. Test moderately: follow run tests, full suite only when shared code is touched. Validate before handing off.
- careful: ask immediately, small verified steps, approval before touching real data.
- pair: fast high-volume edits with an edit log and light checks while the user reviews live.
- afk: ask everything up front, then run unattended until done or blocked.
Doc shape: This skill points at other skills (add-tests, run-tests, verify-commit) instead of inlining every instruction—modular by choice; if that becomes hard to follow, a future option is one consolidated runbook.
Stop only for
- Blocker — decision, access, ambiguity, or rule that forbids proceeding (dependency-safety.mdc, data-safety.mdc, …).
- Owner-only items in
open-questions.md, plan, or tasks. - No viable path after reasonable retries.
Otherwise keep going.
First action: blockers
- Scan conversation, plan,
open-questions.md, tasks for owner-only items. - If blocking → list and stop; else proceed.
Issues
If there is a plan, and neither the phase about to start nor the plan (an Issues: line under its title) has an Issues: line, create the issue with plan issues before starting. A plan-level line covers every phase without its own, so a plan that is one issue is handled once. It runs without asking, once (the line it writes stops repeats), and stays quick. Skip without comment when the repo has no GitHub remote or gh is not signed in.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed · +6 lines 58346f04e9a9
- 22d ago Changed · +10 lines · +17 tokens per session a1e59db4ede2
- 1mo ago First seen · 76 lines · 58 tokens per session scan A 245aab8fb66e
run-task-loop is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 75 tokens to every session and 1,578 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-08-31.
Other skills, from other repositories
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
build-workspace-docs
Use when regenerating README.md and WORKAREAS.md in a managed library workspace. Always dry-run first to preview changes.
update-installed-skills
Use when syncing or updating previously installed skills to their latest version. Always dry-run updates before applying, and check for breaking changes.