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 LucasSantana-Dev/sharekit --skill loop-engineergit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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/lucassantana-dev/sharekit/loop-engineer)<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.
<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>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.00092 | $0.00885 |
| Opus 5.5 | $0.00037 | $0.00354 |
| Sonnet 5.5 | $0.00018 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00089 |
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.
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.
What ships with it
11 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.
- evals/evals.json 6.3 KB
- references/building-blocks.md 4.8 KB
- references/cost-guide.md 2.6 KB
- references/discipline.md 1.6 KB
- references/loop-templates.md 3.6 KB
- references/phase-0-goal.md 1.5 KB
- references/phase-1-2-architecture.md 1.8 KB
- references/phase-3-cycle.md 977 B
- references/phase-4-blocks.md 1.4 KB
- references/phase-5-implementation.md 1014 B
- references/phase-6-handoff.md 1.1 KB
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 · 88 lines · 92 tokens per session scan A 88348ddb2cfd
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.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
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.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.