Loop Engineering is a collection of patterns, starter projects, and command-line tools for designing recurring workflows around AI coding agents. It is for developers who want agents to discover work, make changes, verify results, and preserve project state across tasks. The catalogue entries provide the project's reusable skills, agents, plugin, and instruction.
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 cobusgreyling/loop-engineering --skill install-loopgit clone --depth 1 https://github.com/cobusgreyling/loop-engineeringWrote 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/cobusgreyling/loop-engineering/install-loop)<a href="https://agentmods.dev/skills/cobusgreyling/loop-engineering/install-loop"><img src="https://agentmods.dev/badge/skills/cobusgreyling/loop-engineering/install-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/cobusgreyling/loop-engineering/install-loop"><img src="https://agentmods.dev/badge/skills/cobusgreyling/loop-engineering/install-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 9 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 17 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 27 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 28 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 48 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 54 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 61 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 67 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 74 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 75 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00059 | $0.00735 |
| Opus 5.5 | $0.00024 | $0.00294 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (11,623 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 735 once invoked, about $0.0002 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-30.
Other skills, from other repositories
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.
hive-work-loop
The core agent work cycle in Hive — from finding a task through claiming, launching a run, handling approvals, finishing, and promoting. Use this skill for task-first project work, governed runs, and clean handoff.
hive-project-setup
Set up and configure Hive workspaces, projects, tasks, and evaluator policy. Use this skill when bootstrapping, creating projects, managing tasks, or configuring PROGRAM.md.
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.