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 telagod/code-abyss --skill loop-engineeringgit clone --depth 1 https://github.com/telagod/code-abyssWrote 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/telagod/code-abyss/loop-engineering)<a href="https://agentmods.dev/skills/telagod/code-abyss/loop-engineering"><img src="https://agentmods.dev/badge/skills/telagod/code-abyss/loop-engineering/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/telagod/code-abyss/loop-engineering"><img src="https://agentmods.dev/badge/skills/telagod/code-abyss/loop-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00097 | $0.00519 |
| Opus 5.5 | $0.00039 | $0.00208 |
| Sonnet 5.5 | $0.00019 | $0.00104 |
| Haiku 4.5 | $0.00010 | $0.00052 |
Grade A, and why
loop-engineering 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.
What it actually says
Loop — the engineering cycle: select, advance, distill, deliver
Rule content lives in the four files below; this SKILL.md only routes
(doctrine/04-maintenance.md governs edits to this bundle too).
Route by moment
| You are about to… | Read (in this folder) |
|---|---|
| Start a session; choose the next unit; size it; decide who/which tier runs it | select.md |
| Push a unit forward; wonder if you're stalled; pace an unattended run | advance.md |
| Decide where a learning goes — lesson, memory, project-level skill, or nowhere | distill.md |
| Claim a unit done; commit; report; end the session | deliver.md |
A full pass is select.md → advance.md → distill.md → deliver.md, once per unit
of work; re-enter at select.md §5 after each landing.
Scope and neighbors
This bundle is the outer cycle that sequences the others across a session and a
project. Whether/how to delegate and judge (escalate, done-gate, ask-user) is
doctrine; how to work a problem once inside a unit (investigate, design, execute,
verify, write) is methods; domain judgment is the matching domain bundle. When this
bundle and doctrine both fire, doctrine first — its three non-negotiables apply
inside every phase of the loop.
The stance
A project advances as a sequence of landed loops, and compounds only if each loop
distills. Progress is landed deliverables, not activity (advance.md §3); the next
session's speed is this session's runway (deliver.md §4); and the institution grows
one filed learning at a time (distill.md §1) — that is how weak sessions get strong.
What ships with it
4 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.
- 1mo ago First seen · 39 lines · 97 tokens per session scan A 31a7eb677d42
loop-engineering is a skill published in the GitHub repository telagod/code-abyss (244 stars, last pushed 3mo ago), licensed MIT. It adds 97 tokens to every session and 519 once invoked, about $0.0004 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
fast-resume
Search local coding-agent session history and identify safe resume commands. Use when the user asks to find, inspect, continue, or recover previous work from Claude Code, Codex, Pi, or another agent indexed by fast-resume.
claude-code-expert
Especialista profundo em Claude Code - CLI da Anthropic. Maximiza produtividade com atalhos, hooks, MCPs, configuracoes avancadas, workflows, CLAUDE.md, memoria, sub-agentes, permissoes e integracao com ecossistemas.
retro
A session-review workflow that examines what happened in a coding session and proposes changes to the coding environment. It reports evidence-backed improvements but does not edit files itself.
codexkit-daily-brief-generator
Create a concise daily briefing from calendar items, tasks, messages, and open decisions. Use at the start of a workday to identify priorities, risks, preparation needs, and follow-ups.
codexkit-meeting-summary-generator
Summarize meeting notes or transcripts into decisions, action items, owners, risks, and follow-up messages. Use after meetings when raw notes need a clean recap.
codexkit-onboarding-checklist-creator
Create practical role-specific onboarding checklists with owners, timing, access needs, and first-week milestones. Use for new hire, contractor, client, or team onboarding.