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/cobusgreyling/loop-engineering/install-loopnpx skills add cobusgreyling/loop-engineering --skill install-loopgit clone --depth 1 https://github.com/cobusgreyling/loop-engineeringWhat 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.00059 | $0.00735 |
| Opus 5 | $0.00030 | $0.00367 |
| Sonnet 5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
install-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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install Loop Engineering
Goal
Leave the repo with a scaffolded report-only loop, a Loop Ready score, and clear next actions — using the single CLI:
npx @cobusgreyling/loop
Do not deprecate or remove existing loop-init / loop-audit usages you find; both doors stay valid. Prefer loop for new work.
Steps
-
Detect context
- If
LOOP.mdorSTATE.mdalready exists, run doctor only (skip init unless human asks to re-scaffold):npx @cobusgreyling/loop doctor . --json npx @cobusgreyling/loop status . - Otherwise continue.
- If
-
Pick pattern (default:
daily-triage)Pain Pattern Morning chaos / unclear priorities daily-triagePRs stalling pr-babysitterCI red / flakes ci-sweeperCVE / Dependabot noise dependency-sweeperPost-merge TODOs post-merge-cleanupStale release notes changelog-drafterNoisy issues issue-triageOne GitHub Action, almost no files thin-loop -
Pick tool —
claude|grok|codex|opencode(defaultclaude). -
Scaffold
npx @cobusgreyling/loop init . --pattern <pattern> --tool <tool>Optional harness (only if human wants Foundry): add
--with-foundry. -
Doctor
npx @cobusgreyling/loop doctor .- Exit
0= healthy ·1= warnings ·2= blocked - Follow the top 3 printed actions; do not invent extra architecture.
- Exit
-
Cost check before high-cadence schedules:
npx @cobusgreyling/loop cost -p <pattern> -l L1 -c 1d -
Week-one rule
- Report only. No auto-fix, no auto-merge.
- Tell the human the first
/loopor scheduler command from init output. - Suggest badge only when score is strong:
npx @cobusgreyling/loop badge .
Compatibility
These remain fully supported (do not rewrite existing docs/scripts unless asked):
npx @cobusgreyling/loop-init .
npx @cobusgreyling/loop-audit . --suggest
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 · 82 lines · 59 tokens per session scan A 294cdff785a1
install-loop is a skill published in the GitHub repository cobusgreyling/loop-engineering (10,738 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 735 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-30.
Other skills, from other repositories
aw-author
Author, validate, and improve GitHub Agentic Workflow (gh-aw) markdown files. Use when the user wants to create a new workflow, validate an existing workflow, improve a workflow, or debug workflow issues. Triggers on: "aw-author", "agentic workflow", "gh-aw workflow", "workflow markdown", "workflow frontmatter"…
aw-daily
Fully autonomous daily pipeline for the aw-author plugin. Executes intelligence research (web search + GitHub activity queries), posts to Discussions, performs gap analysis against reference files, creates issues, implements changes on develop branch, creates PR, requests review, and auto-merges. Designed for…
gh-aw-report
Daily intelligence reporting for the GitHub Agentic Workflows (gh-aw) ecosystem. Executes 8+ targeted web searches, synthesizes findings into a structured Markdown report, updates the persistent knowledge base, and optionally posts to GitHub Discussions. Triggers on: "aw-report", "gh-aw report", "intelligence sweep"…
hive-maintainer
Discipline for developing Hive itself — PR sizing, review handling, merge discipline, release workflow, delegation, and cleanup hygiene. Use this skill when working on Hive repo changes that span multiple PRs or review cycles.
hive-coordination
Coordinate work across multiple agents and projects in Hive. Covers task claims, blockers, handoffs, campaigns, portfolio management, briefs, and shared memory.
hive-essentials
Hive mental model and orientation. Read this first before using any other Hive skill. Covers the entity hierarchy, observe-and-steer pattern, drivers, sandboxes, console vs CLI, and workspace conventions.