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-watchgit 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-watch)<a href="https://agentmods.dev/skills/lubluniky/dale/dale-loop-watch"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-loop-watch/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-watch"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-loop-watch.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.00057 | $0.00285 |
| Opus 5 | $0.00028 | $0.00143 |
| Sonnet 5 | $0.00011 | $0.00057 |
| Haiku 4.5 | $0.00006 | $0.00028 |
Grade A, and why
dale-loop-watch 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 3d 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 Watch
Build a change detector, not a scheduled summary generator.
Workflow
- Define the source, cadence, baseline, meaningful-change predicate, allowed action, notification destination, expiry, and failure limit.
- Confirm the source can be read reliably and that the action does not exceed the user's authority.
- Persist the minimum comparable state: timestamp, normalized observation, source identity, and last emitted event.
- On each wakeup, fetch fresh state and compare it to the baseline. Ignore formatting noise, reordered data, and unchanged results.
- If no meaningful change occurred, update only necessary health metadata and remain quiet.
- If the predicate matches, capture evidence, perform the authorized action or notify once, update the baseline, and decide whether to continue.
- Back off and escalate after repeated source/auth failures. Never interpret inability to read the source as “no change.”
- Disable scheduled work when the expiry or terminal condition is reached; archive the user task only when requested.
Use the product's automation mechanism. Do not implement cadence with a blocking shell loop.
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.
- 3d ago Changed d947915d4237
- 11d ago First seen · 22 lines · 57 tokens per session scan A 682ddf164f0c
dale-loop-watch is a skill published in the GitHub repository lubluniky/dale (51 stars, last pushed 4d ago), licensed MPL-2.0. It adds 57 tokens to every session and 285 once invoked, about $0.0003 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
meeting-note-summarizer
Turn meeting notes or transcripts into factual summaries, decisions, questions, and action items. Use when a user wants a concise recap or needs explicit owners and deadlines extracted without filling in missing details.
daily-standup-journal
Generate concise daily standups, reflection prompts, and weekly retrospectives for individuals or teams. Use for planning a day, surfacing blockers, reviewing user-provided entries, or drafting a check-in without assuming prior history.
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
agency-os
Notion-as-source-of-truth dispatch board for running your work like an AI agency. One Tasks database is the source of truth; tasks flow Suggestion through Discussion, To-Do, In Progress, and Done with subtasks, recurring cadences, dependencies, and template subtrees. Batch execution fans approved To-Do rows out to…
atmos-custom-commands
Custom CLI commands: command definition in atmos.yaml, arguments, flags, shared native step types, when: conditions, output/UI steps, env vars, custom component types.
workflow
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use…