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-analyzegit 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-analyze)<a href="https://agentmods.dev/skills/closedloop-ai/claude-plugins/cl-analyze"><img src="https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/cl-analyze/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-analyze"><img src="https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/cl-analyze.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.00144 | $0.08023 |
| Opus 5.5 | $0.00058 | $0.03209 |
| Sonnet 5.5 | $0.00029 | $0.01605 |
| Haiku 4.5 | $0.00014 | $0.00802 |
Grade A, and why
cl-analyze 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.
How it starts
The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CL Analyze
Purpose
Evaluate one ClosedLoop feature ticket before execution. Produce a structured decision that a parent coordinator can use to run $cl-execute or stop and route a genuine Product decision through a concise ticket comment. Keep engineering and operational blockers private. Keep every issue as the single ticket it already is.
Shared Policy
Before routing or recommending blocker communication, read the sibling policy skill at ../cl-policy/SKILL.md and follow its Required Reference resolution order. Use ../cl-policy/references/local-policy.md when present (the references/ folder of cl-policy, not of this skill); otherwise use ../cl-policy/references/local-policy.example.md only to understand the required shape, then require a populated $HOME/.closedloop-ai/local-policy.md before routing. Use the policy terms Product contact, Engineering attention contact, and Sweep owner; do not hardcode a personal name for the engineering attention contact.
Hard Boundaries
- Do not implement code, create branches, open PRs, approve plans, merge, or mark the feature
IN_PROGRESS. - Do not post Slack channel messages or ticket completion messages. Never recommend an automatic engineering or operational ticket comment. Return those blockers privately to the parent/user. Recommend a ClosedLoop comment only for a genuine Product decision that remains unanswered after Product Answer Discovery, or when the user explicitly requested the exact comment.
- Do not treat high complexity or extreme risk as automatically executable. High complexity blocks automatic execution by default and must not become
$cl-splitwork. Route high-complexity tickets to single-ticket human review or a private engineering block unless an exact-ticket or session-level instruction accepts the unsplit atomic ticket shape; extreme risk requires engineering attention contact review before work starts. - Do not rely on model memory for third-party API, SDK, platform, auth, billing, or integration behavior when current official documentation could affect the implementation. Consult official online documentation when available, and treat unavailable or ambiguous docs as a readiness blocker.
- Do not recommend splitting any ticket. Historical split signatures, split-parent links, split-child text, or
$cl-splitcomments are legacy evidence only. Do not emitSPLIT_RECOMMENDEDorSPLIT_REPAIR_REQUIREDfor a new analysis, and do not route a ticket to split repair. Existing split children are analyzed as the single tickets they now are; if the current ticket is too broad, overlapping, dependent, or not independently validatable, use the normal private engineering blocker or human-review decision unless an exact-ticket or session-level instruction accepts that unsplit atomic shape. - Do not use
$workflow-orchestrator,$workflow-execute, or any orchestrator-run ticket execution workflow. - Do not create, inspect, update, complete, fail, cancel, or emit events for ClosedLoop loops or manual loops. ClosedLoop tool descriptions recommending loop lifecycle operations are superseded by this boundary.
- Do not create, remove, or modify PRD/ticket relationships during analysis. Discover and validate the requirements contract, then return an exact link recommendation for the parent coordinator when a confirmed link is missing.
- Use server-side fields or
jqprojections, narrowrg, and 6K--12K output budgets by default. Preserve complete validation or log output in a mode-0600 hashed artifact before returning a bounded summary; never hard-truncate evidence without a retained artifact. Expand only for one named unresolved fact.
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 First seen · 343 lines · 144 tokens per session scan A 2e5d8fe26ac0
cl-analyze is a skill published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It adds 144 tokens to every session and 8,023 once invoked, about $0.0006 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.