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-prgit 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-pr)<a href="https://agentmods.dev/skills/lubluniky/dale/dale-loop-pr"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-loop-pr/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-pr"><img src="https://agentmods.dev/badge/skills/lubluniky/dale/dale-loop-pr.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.00369 |
| Opus 5.5 | $0.00014 | $0.00148 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
dale-loop-pr 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.
What it actually says
Dale Loop PR
Resolve the exact PR, current head, repository instructions, checks, review findings, scope, and mergeability. Record artifact identity and current blockers.
Use a read-only subagent for independent review when it adds meaningful coverage; inherit model settings and supply the requirement, diff, and evidence. Do not prime its verdict or allow further delegation. The coordinator or one scoped worker repairs valid findings and PR-caused failures. Create separate Codex tasks only when explicitly requested.
Preserve unrelated changes. Commit and push only within the user's publication authority; do not treat a monitoring-only request as permission to repair. After a changed head, refresh GitHub state and re-review affected risks. Retain valid evidence for unchanged behavior only after confirming the dependency scope.
Declare merge-ready only when required checks pass, review has no unresolved actionable findings or active change requests, scope is correct, and the PR is mergeable. Merge only when requested. Change approach after repeated unchanged failure; report concrete blockers without treating silence as approval.
Use an automation for requested later checks. Persist head, findings, actions, and terminal condition; re-observe on wake and stay quiet while unchanged. Do not assume workers remain alive between wakeups.
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.
- 1mo ago Changed · +16 lines · -26 tokens per session 79370a39ce0b
- 1mo ago First seen · 22 lines · 62 tokens per session scan A f6eff55d0f41
dale-loop-pr is a skill published in the GitHub repository lubluniky/dale (54 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 36 tokens to every session and 369 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
pr-body
A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.
gitlab-create-mr
Create GitLab merge requests from a local branch using a reviewable workflow for branch checks, GitLab host detection, diff analysis, title and description writing, and glab mr create. Use when opening a GitLab merge request, drafting or improving merge request copy, preparing a branch for review, or working across…
code-review
Request or perform a git-backed code review for a defined diff or SHA range using implementation context and requirements. Use when finishing a task, completing a major feature, preparing to merge, or when you need a fresh review before proceeding.
loop-converge
Use only when the user explicitly invokes /loop-converge or names this skill. Authors a loop-converge run. Do not use unless named. Do not execute or resume generated runtime node files.
git-guardar
Spec versión: vitals/specs/project-version.md.
dt-bootstrap
Convierte el template El DT en la base de tu propio proyecto: lo promueve a la raíz, suelta el remoto del template y deja el repo listo para tu trabajo. Es una operación irreversible → cae bajo el gate duro (vitals/specs/precedence.md): siempre dry-run + confirmación explícita + working tree limpio.