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 closedloop-ai/claude-plugins --skill cl-executegit clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWrote 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/closedloop-ai/claude-plugins/cl-execute)<a href="https://agentmods.dev/skills/closedloop-ai/claude-plugins/cl-execute"><img src="https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/cl-execute/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/closedloop-ai/claude-plugins/cl-execute"><img src="https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/cl-execute.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.00172 | $0.05674 |
| Opus 5.5 | $0.00069 | $0.02270 |
| Sonnet 5.5 | $0.00034 | $0.01135 |
| Haiku 4.5 | $0.00017 | $0.00567 |
Grade A, and why
cl-execute 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 yesterday.
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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CL Execute
Purpose
Draft the required ClosedLoop-linked implementation plan, then execute one
functional feature as a long-running goal. A feature is one complete selected
user-facing page or capability delivered end to end, not automatically an
entire PRD. It may be one ticket or one coherent multi-ticket unit explicitly
selected by $cl-sweep; all member tickets and shipping surfaces required for
that page or capability belong in one integrated pull request. Other pages or
capabilities from the same PRD and separately owned shared-foundation
prerequisites may remain outside this feature boundary.
$cl-execute <ClosedLoop feature URL or FEA/ISS slug>
$cl-execute batch: <ticket URL> <ticket URL> ...
$cl-analyze decides whether work is ready and whether a plan approval gate is
required. $cl-execute owns plan drafting, plan review, upload/link, revision,
approval-or-wait disposition, implementation, the two-pass coordinated
code-review sequence, validation, PR handoff, merge disposition, and ticket/
plan reconciliation.
Treat the invocation as standing approval to create and approve the implementation plan after worker review, create a PR, address PR feedback, merge once CI is green and the PR is ready, and mark the feature done after merge. This approval applies only after the readiness gate passes and no human UI plan approval is required. It does not authorize high-complexity execution without an exact-ticket override, extreme-risk work, incoherent batches, duplicate/stale or blocked work, UI implementation without required human plan approval, manual CI or review triggers, or externally visible engineering/operational comments.
Do not post completion messages.
Sweep display activity
When invoked within a sweep, follow display events for both Desktop and CLI owners: report actual planning, coding, review and human-wait entry, and clear the phase on exit. Logging failures do not block work. Publish verified business status after existing authenticated ClosedLoop ticket reads, without additional wallpaper queries. Report explicitly established or cleared ticket dependencies using that reference.
What ships with it
13 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.
- agents/openai.yaml 1.2 KB
- references/cross-family-review.md 8.1 KB
- references/feature-manual-qa.md 9.2 KB
- references/implementation-review-pr.md 35 KB
- references/monitoring-merge-completion.md 7.4 KB
- references/planning-and-gates.md 27 KB
- references/result-formats.md 12 KB
- references/support-lanes-and-sweeps.md 8.1 KB
- references/writing.md 2.5 KB
- scripts/check-plan.mjs 10.0 KB runs code
- scripts/check-plan.test.mjs 7.0 KB runs code
- scripts/decision-log.sh 2.5 KB runs code
- scripts/decision-log.test.mjs 1.8 KB runs code
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.
- yesterday Changed bd3e5168d3c4
- 4d ago First seen · 381 lines · 172 tokens per session scan A e2d42f1c5122
cl-execute is a skill published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It adds 172 tokens to every session and 5,674 once invoked, about $0.0007 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-10-06.
Other skills, from other repositories
file-a-task
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
fleet
The session roster (/foundry:fleet) — native /list-agents annotated with each row's foundry programme, over the NATIVE session/container list. Read-only/advisory. Trigger to see all your parallel sessions and containers at a glance with their foundry context, or when supervising many sessions and asking "what is each…
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.