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 skillmds/skillmd --skill repo-task-proof-loopgit clone --depth 1 https://github.com/skillmds/skillmdWrote 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/skillmds/skillmd/repo-task-proof-loop)<a href="https://agentmods.dev/skills/skillmds/skillmd/repo-task-proof-loop"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/repo-task-proof-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/skillmds/skillmd/repo-task-proof-loop"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/repo-task-proof-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.00069 | $0.03317 |
| Opus 5.5 | $0.00028 | $0.01327 |
| Sonnet 5 | $0.00014 | $0.00663 |
| Haiku 4.5 | $0.00007 | $0.00332 |
Grade A, and why
repo-task-proof-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 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.
This is a copy
100% identical to repo-task-proof-loop — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Task Proof Loop
Use this skill when the user wants a repeatable, auditable implementation workflow for a non-trivial coding task, especially a feature, refactor, migration, or bug fix that should leave repo-local proof in .agent/tasks/<TASK_ID>/.
All task artifacts created by this workflow must stay inside the repository.
When the examples below mention scripts/task_loop.py, that path is relative to this skill root. Run it while your shell working directory is inside the target repository.
What this skill does
- Initializes a strict repo-local task folder under
.agent/tasks/<TASK_ID>/ - Seeds or updates the required artifact files
- Installs project-scoped Codex and Claude subagent templates into
.codex/agents/and.claude/agents/ - Updates the repo-root
AGENTS.mdCodex baseline plus the repo's Claude guide file (CLAUDE.mdor.claude/CLAUDE.md) with a managed block that explains the workflow - Guides the agent through a strict loop:
- spec freeze
- builder implementation
- evidence packing
- fresh verification
- minimal fix
- fresh verification again until
PASS
See:
references/REFERENCE.mdreferences/COMMANDS.mdreferences/SUBAGENTS.mdreferences/SCHEMAS.md
Commands this skill supports
Treat the following words as commands when the user invokes this skill:
init <TASK_ID>: create.agent/tasks/<TASK_ID>/, install or refresh subagent templates, and updateAGENTS.mdplus the repo's Claude guide filefreeze <TASK_ID>: create or refinespec.mdfrom the user task, task file, and repo guidancebuild <TASK_ID>: implement the task against the frozen specevidence <TASK_ID>: create or refreshevidence.md,evidence.json, and raw artifacts without changing production codeverify <TASK_ID>: run a fresh verifier pass and writeverdict.json, plusproblems.mdwhen neededfix <TASK_ID>: apply the smallest safe fix set fromproblems.md, then refresh the evidence bundlerun <TASK_ID>: execute the full loop from spec freeze through verificationstatus <TASK_ID>: summarize current artifact status
What ships with it
6 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.
- 4d ago First seen · 257 lines · 69 tokens per session scan A 7ce5da248131
repo-task-proof-loop is a skill published in the GitHub repository skillmds/skillmd (1 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 3,317 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to repo-task-proof-loop, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
diet-remove
Remove a dependency identified by uzomuzo diet — analysis + issue (default) or direct PR.
review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.
aiox-review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.
intent-verify
Verify current requirements against implementation and actual results across a product or change scope, including completed features. Run permissible existing checks and report findings without fixes.
verify
Verify phase deliverables match acceptance criteria.