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/thaitype/chief/chief-loopnpx skills add thaitype/chief --skill chief-loopgit clone --depth 1 https://github.com/thaitype/chiefWrote 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/thaitype/chief/chief-loop)<a href="https://agentmods.dev/skills/thaitype/chief/chief-loop"><img src="https://agentmods.dev/badge/skills/thaitype/chief/chief-loop.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.00070 | $0.01285 |
| Opus 5 | $0.00035 | $0.00642 |
| Sonnet 5 | $0.00014 | $0.00257 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
chief-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 2d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run chief-agent across the full milestone — batch after batch — until both the goals and the contracts are satisfied, recording a decision-aware report for every task instead of one combined report per batch.
This builds directly on chief-autopilot's auto mode. If you want the "stop and ask a
human on ambiguity" behavior, use chief-autopilot safe instead — chief-loop only runs
in auto mode; it doesn't have a safe-mode equivalent.
Prerequisite Check
Before doing anything:
- Identify the active milestone directory under
.chief/. - Check that
_goal/has at least one non-empty file. - Check that
_contract/has at least one non-empty file.
If either is missing → STOP. Tell the user:
"Goals and contracts are required for chief-loop. Run
/chief-planfirst."
Do NOT proceed.
Entry Confirmation
Present the current goals and contracts to the user in a brief summary (file names + 1-line description each).
Ask one question:
"Goals and contracts look correct? Proceed with chief-loop, or use
/chief-planto revise first?"
If the user says revise → stop. If the user confirms → proceed.
Optional: if the loop-readiness skill is available, offer to run it against this
milestone's plan before proceeding — it reviews whether the plan has enough
feedforward/feedback coverage to run safely unattended. This is a suggestion, not a
requirement; proceed without it if the user declines.
Outer Loop (spans as many batches as it takes)
1. Create or update TODO
Read existing _plan/_todo.md if present. Create the next batch of 3–5 tasks based on
goals, contracts, and what's already done — same small-batches principle as
chief-autopilot.
Write _plan/_todo.md. Do NOT wait for approval — this is autopilot-style, no pausing
for plan review.
2. Work the batch, one task at a time
For each uncompleted task in the current batch:
- Delegate to builder-agent with:
- The TODO entry
- Milestone goals (
_goal/) - Milestone contracts (
_contract/) - Relevant global rules (
.chief/_rules/) - Verification expectations
- Wait for builder to complete.
- If builder reports a blocker or ambiguity, see Handling Ambiguity below before moving on.
- Mark the task
[x]in_todo.md. - Write that task's report (see Task Report below) — do this immediately, before starting the next task. Don't batch report-writing up to the end.
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.
- 2d ago First seen · 139 lines · 70 tokens per session scan A 6cda4b4863c8
chief-loop is a skill published in the GitHub repository thaitype/chief (59 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 1,285 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…