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 lubluniky/dale --skill dale-loop-goalgit clone --depth 1 https://github.com/lubluniky/daleWrote 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/lubluniky/dale/dale-loop-goal)<a href="https://agentmods.dev/skills/lubluniky/dale/dale-loop-goal"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-loop-goal/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/lubluniky/dale/dale-loop-goal"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-loop-goal.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.00036 | $0.00304 |
| Opus 5 | $0.00018 | $0.00152 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
dale-loop-goal 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 4d 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
Dale Loop Goal
Keep one objective coherent across work and resumptions. State the completion predicate and current evidence, then take the smallest useful next action. Use subagents only when independent work emerges; inherit model settings and keep a single coordinator. Do not turn sequential work into a swarm.
Use the goal tool only when a goal was explicitly requested. Follow its live status and blocking rules; set a token budget only if the user supplied one. For a requested later wakeup, use an automation instead of a blocking sleep. Persist enough state to re-observe the actual target before the next action.
Continue through authorized work. Ask for missing authority or a consequential choice only when needed and finish unaffected work meanwhile. When the same failure repeats without new evidence, change approach rather than retry harder. Honor user limits and the goal tool's exact completion/blocking semantics.
Finish with the outcome, direct evidence, and any actual unmet condition.
Cancellation and changed scope
On cancellation or revoked scope, interrupt affected workers immediately before other work, invalidate pending outputs, and preserve existing changes. Update or disable related scheduled work only within the user's cancellation scope. For a correction, stop conflicting work first, then send the revised contract; accept subsequent results only against the current request and artifact state.
What ships with it
1 file 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.
- 4d ago Changed · +10 lines · -15 tokens per session 2d7ae44848ec
- 11d ago First seen · 22 lines · 51 tokens per session scan A 132817de7d09
dale-loop-goal is a skill published in the GitHub repository lubluniky/dale (51 stars, last pushed 5d ago), licensed MPL-2.0. It adds 36 tokens to every session and 304 once invoked, about $0.0002 per session on Opus 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
agent-creation-skill
Procedural guide for creating new agents from templates when project complexity requires delegation.
memory-fabric
Knowledge graph orchestration layer with entity extraction, natural language query parsing, deduplication (>85% similarity), and cross-reference boosting. Unifies search results ranked by recency, relevance, and authority. Use when designing memory retrieval, building entity graphs, or optimizing knowledge graph…
loop-graph
Compile one durable loop-graph run into executor, ledger, directives, ops, and supervisor artifacts under a dated .longgraph directory, then present copy-ready host prompts. Use directly for a custom multi-round shape with gated milestones, independent audit, cross-host execution, or durable state; focused sibling…
longgraph
Route and author durable long-horizon loop-graph runs. Use for multi-round work needing durable state, gated milestones, owner boundaries, host switching, or independent audit. Route code cleanup to /loop-converge, feature requirements to /loop-deliver, and evidence-backed solution comparison to /loop-research; use…
loop-converge
Author and optionally direct-launch a two-node loop-graph run whose North Star is code convergence — delete unused code, merge duplicates, reuse, slim. Use when the user invokes /loop-converge, or asks to loop on dead code, duplication, unused exports, DRY cleanup, or merging twin implementations. Starts the owner…
loop-deliver
Author and optionally direct-launch a two-node loop-graph run for implementing a product or engineering requirement through verified vertical slices. Use when a requested feature, integration, migration, or behavior change needs multiple rounds, durable acceptance proof, and independent audit. Not for code cleanup…