loop-llm SKILL.md skillA
loop-llm from grisuno/lazyown is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add grisuno/lazyown/loop-llm@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- grisuno/lazyown
- Path
skills/loop-llm/hermes/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 14, 2026
- Size
- 5,477 bytes
- Repository stars
- 300
- License
- AGPL-3.0
Add a new LLM leg to LazyOwn loop mode in one shot. Knows the pool-member contract, factory spec-prefix rule, priority/backfill semantics and validation tests.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /loop-llm
Add one LLM leg to loop mode so `auto_loop` / `lazy_loop` fail over through it.
No iteration: follow the contract, wire the leg, update the defaults, run the self-check.
## Usage
```
/loop-llm pi
```
## Step 1 — The contract (read before touching code)
Loop mode asks the pool, never a backend directly:
- `modules/lazy_loop.py` `LlmPool.DEFAULT_MEMBERS` — the 5 legs, each
`{"name": <unique-id>, "model": "<prefix>:<model-id>", "priority": <int>}`.
Higher priority tries first; equal priority round-robins via the `rr`
cursor in `sessions/lazy/llm_pool.json`.
- `LlmPool.complete()` resolves each member's `model` spec through
`modules.llm_factory.complete(spec, prompt, max_tokens)`.
- `complete()` accepts a `backend:` prefix. Registered factory backends
(`SUPPORTED_BACKENDS`) plus leg-only prefixes (`toposwarm:`, `pi:`) are
valid. Leg-only prefixes are the correct choice for agent CLIs and
routers: they need NO entry in `SUPPORTED_BACKENDS`, NO payload-schema
key, and NO change to `test_llm_contract.py` (which pins the canonical
backend tuple).
- Dead legs MUST raise `RuntimeError` (never return `""` on outage):
…Read the whole file at its exact version.
How to install
mdr add grisuno/lazyown/loop-llm@sha256:806fdb07dede9dcaThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ipesgmqnlpzxgjfj)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 14, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5477 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
grisuno/lazyown · 300 stars · license AGPL-3.0 · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ipesgmqnlpzxgjfj GET https://markdownregistry.com/api/v1/resolve?ref=grisuno/lazyown/loop-llm GET https://markdownregistry.com/api/v1/blob/806fdb07dede9dcabd4f870bdacad11610e0702172c9aa5ea0ce32c0310a9fcd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.