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 skills add sago-cream/human-out-of-loop --skill solve-issuegit clone --depth 1 https://github.com/sago-cream/human-out-of-loopWrote 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/sago-cream/human-out-of-loop/solve-issue)<a href="https://agentmods.dev/skills/sago-cream/human-out-of-loop/solve-issue"><img src="https://agentmods.dev/badge/skills/sago-cream/human-out-of-loop/solve-issue/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/sago-cream/human-out-of-loop/solve-issue"><img src="https://agentmods.dev/badge/skills/sago-cream/human-out-of-loop/solve-issue.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.00053 | $0.00614 |
| Opus 5 | $0.00026 | $0.00307 |
| Sonnet 5 | $0.00011 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
solve-issue 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 11d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Select
$solve-issue #<positive-issue-number>: solve that issue in the current task; never create a worker or substitute another issue.$solve-issue <positive-amount>: select that many distinct eligible issues in ascending order and immediately create one sidebar-visible task per issue in parallel. If fewer qualify, dispatch all remaining eligible issues and report the shortage.$solve-issue: solve one eligible issue in the current task.
Eligible: open, with no open or draft PR covering it through a GitHub Development link or closing keyword. Ignore incidental mentions. Recheck once before dispatch.
Exact-target failure:
ISSUE_SKIPPED issue=<number> reason=<not_found|not_open>
ISSUE_SKIPPED issue=<number> reason=covered_by_pr pr=<url>
Dispatch
- Keep exact and default runs in the invoking task. For amount runs, use only the selected issue tasks; do not create separate developer, reviewer, or publication tasks.
- Give every issue an isolated worktree and branch named
<type>/<short-kebab-description>, using the narrowest offix,feat,docs,refactor,test, orchore. Never namespace it. - Call
set_thread_titleonce per task and never change it:- Exact/default task:
Solve #<issue> - Amount orchestrator:
Solve <amount> issues - Amount worker:
#<issue>: <short-description>
- Exact/default task:
- Give each amount worker the repository, issue + URL, base, branch, absolute worktree, and optional media path. The orchestrator only dispatches, waits, reports terminal results, and resumes existing workers without duplicating them.
Solve
Each issue-owning task completes the whole workflow:
- Activate
$ponytailat full intensity. - Implement the issue, run relevant checks, and commit the complete solution.
- For UI changes, keep
.codex-pr-media/untracked through.git/info/excludeand capture matched, reproducible before/after media: video for interaction, motion, or multiple steps; images otherwise. - Require a clean worktree except ignored PR media, then run
$pr. - If
$prfinds actionable problems, fix and commit them, rerun checks, and invoke$pragain. Repeat in the same task until it publishes a draft PR. - Report the issue, published head, PR URL, and checks. Never merge or mark a PR ready.
What ships with it
1 file 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.
- 11d ago First seen · 43 lines · 53 tokens per session scan A dea13e05f67b
solve-issue is a skill published in the GitHub repository sago-cream/human-out-of-loop (6 stars, last pushed 22d ago), licensed MIT. It adds 53 tokens to every session and 614 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
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.