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-policygit 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-policy)<a href="https://agentmods.dev/skills/closedloop-ai/claude-plugins/cl-policy"><img src="https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/cl-policy/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-policy"><img src="https://agentmods.dev/badge/skills/closedloop-ai/claude-plugins/cl-policy.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.00081 | $0.01808 |
| Opus 5.5 | $0.00032 | $0.00723 |
| Sonnet 5.5 | $0.00016 | $0.00362 |
| Haiku 4.5 | $0.00008 | $0.00181 |
Grade A, and why
cl-policy 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CL Policy
Purpose
Provide the shared local access and routing policy for ClosedLoop ticket automation. This skill keeps team-specific names, communication rules, and tool-access fallbacks out of the execution skills, while allowing the skill pack to be shared with either a populated bundled policy or a local machine override.
ClosedLoop Tool Access
When ClosedLoop tools are absent from the initial tool list, do not conclude that ClosedLoop or its MCP server is unavailable.
- Use dynamic tool discovery or
tool_searchfirst when the current host explicitly supports dynamic calls. Search by capability, such asClosedLoop get document,list document comments,document versions, ordocument relationships. Codex CLI's TUI does not currently execute dynamic tool calls: in that surface, use statically exposed MCP tools or the CLI/API fallback below and never emit a dynamic tool call merely because a skill says to discover by capability. - Do not hardcode an MCP prefix such as
mcp__closedloop. The prefix depends on the user's configured MCP server name and may legitimately differ. - If dynamic discovery is unavailable or cannot see the configured server, try the user's Codex CLI MCP configuration before declaring an access blocker.
- If MCP access is still unavailable and
CLOSEDLOOP_API_KEYis present, use the production ClosedLoop API directly. Load the key silently from the current environment or the user's shell profile; never print, echo, log, serialize, or include it in command output, memory, prompts, or reports. - Prefer read-only API requests during analysis. Resolve endpoint and payload
contracts from current repository routes or official current documentation
instead of guessing. A ticket slug can be read through
GET https://api.closedloop.ai/documents/<slug>in the current platform. - Treat an inactive localhost MCP URL, a missing initial registration, or a stale read-only intelligence index as an access-path issue, not proof of a ClosedLoop outage. Continue through the next valid fallback and state which source established live state.
- Report a genuine access blocker only after applicable discovery, Codex CLI MCP, and authenticated API paths have been exhausted or are unavailable.
- For ticket intelligence, discover the read-only
closedloop-graphMCP by capability rather than by configured server name, using only discovery mechanisms supported by the current host. Treat it as the preferred indexed discovery surface for bounded PRD/plan/ split lineage, dependencies, semantic matches, duplicates, related tickets, and PR overlap, and for codebase intelligence including symbols, files, ownership boundaries, dependencies, call/data paths, co-change history, tests, and blast radius. Its results are not live authority: re-fetch material documents, relationships, comments, and status from ClosedLoop and verify code/PR claims against current repository and GitHub state.
What ships with it
3 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.
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 · 135 lines · 81 tokens per session scan A d79d3670d920
cl-policy is a skill published in the GitHub repository closedloop-ai/claude-plugins (122 stars, last pushed today), licensed Apache-2.0. It adds 81 tokens to every session and 1,808 once invoked, about $0.0003 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.