loop-engineer

loop-engineer is a skill for Claude Code from LucasSantana-Dev/sharekit. It costs 92 tokens per session (885 once invoked), scanned A, original, MIT.

A design and implementation method for autonomous agent workflows that discover a task, plan it, act, check the result, and repeat. It treats the workflow as a self-running job rather than a series of manual prompts.

In plain words
What is it for?
Use it to design repeating coding, research, content, CI, or automation workflows that can run through multiple work cycles.
Why use it?
It helps an agent-driven process keep moving toward a defined result with feedback and verification.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions subagents.

Good fit Use it to design repeating coding, research, content, CI, or automation workflows that can run through multiple work cycles.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lucassantana-dev/sharekit/loop-engineer
Install

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.

Any agent
npx skills add LucasSantana-Dev/sharekit --skill loop-engineer
Clone the repo
git clone --depth 1 https://github.com/LucasSantana-Dev/sharekit

Made for: Claude Code.

Wrote 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.

agentmods badge for loop-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/loop-engineer/github.svg)](https://agentmods.dev/skills/lucassantana-dev/sharekit/loop-engineer)
Your own site
<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/loop-engineer"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/loop-engineer/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.

agentmods 80×15 button for loop-engineer

Your own site · 80×15
<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/loop-engineer"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/loop-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 885 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.00885
Opus 5.5 $0.00037 $0.00354
Sonnet 5.5 $0.00018 $0.00177
Haiku 4.5 $0.00009 $0.00089

Measured 1mo ago against content hash 88348ddb2cfd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

loop-engineer 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.

sharekit-profile/.claude/skills/loop-engineer/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Loop Engineer

You are not writing a prompt. You are designing a job — a feedback system that discovers, plans, executes, verifies, and iterates until the work is done, without a human manually driving each step.

Preamble — RAG pre-flight

Before starting any design work, query prior loop designs for this exact task domain. See standards/skill-patterns.md §rag-first and §mount-guard.

mount | grep -q "${DEV_ROOT}" || { echo "BLOCKED: External HD unmounted — RAG unreachable"; exit 1; }
python3 ~/.claude/rag-index/query.py "loop design <task-domain> precedent" --top 5
  • If result shows a loop design for the same domain within the last 24h → surface it, ask user to confirm whether to reuse or start fresh.
  • If no recent match → proceed directly to Phase 0.

Done when: RAG queried; prior loop cited or confirmed absent.


Output schema

Every run of this skill produces exactly these files:

goal-card.md           ← Phase 0: confirmed goal + done-when criterion
architecture.md        ← Phase 1+2: architecture + mode decision with rationale
cycle.md               ← Phase 3: 5-stage cycle mapped to THIS task concretely
building-blocks.md     ← Phase 4: 6 building blocks spec table
implementation.md      ← Phase 5: the actual runnable artifact
reconciliation-template.md ← Phase 6: the loop run output template

Save each file as you complete the phase — do not batch them at the end.


Six-phase workflow

Work through the phases below in order. Each phase produces a named output file. Do not skip phases or merge them.

Phase 0 — Goal Characterization Interview the user (5 questions), synthesize Goal Card, wait for user approval before Phase 1.

Phase 1+2 — Architecture & Mode Decision Decide loop size (single-agent vs. fleet) and mode (closed vs. open). Run critic gate. Confirm decisions with user before Phase 3.

Read the full file on GitHub · 88 lines

Changes

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.

  1. 1mo ago First seen · 88 lines · 92 tokens per session scan A 88348ddb2cfd

Subscribe to this mod's changes

loop-engineer is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 3d ago), licensed MIT. It adds 92 tokens to every session and 885 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-09-03.

Related

Other skills, from other repositories

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

interview

Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.

Hmbown/CodeWhale · 40 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

loongsuite-pilot-insight

A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.

alibaba/loongsuite-pilot · 91 tokens