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 agentmods add skills/pass-agent/loomkin/clacknpx skills add pass-agent/loomkin --skill clackgit clone --depth 1 https://github.com/pass-agent/loomkinWrote 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/pass-agent/loomkin/clack)<a href="https://agentmods.dev/skills/pass-agent/loomkin/clack"><img src="https://agentmods.dev/badge/skills/pass-agent/loomkin/clack.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.00696 |
| Opus 5 | $0.00036 | $0.00348 |
| Sonnet 5 | $0.00014 | $0.00139 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
clack 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clack CLI Skill
Implement robust, user-friendly CLI flows with Clack.
Follow This Workflow
- Identify the implementation target.
- Use
@clack/promptsfor most interactive CLI flows. - Use
@clack/corefor low-level/custom prompt rendering and lifecycle control.
- Load only the relevant references.
- Prompt-centric workflows:
references/prompts-api.md - Low-level/core extension work:
references/core-api.md - UX and reliability review:
references/best-practices.md - Pattern selection and scaffolding:
references/examples.md - Source links and freshness checks:
references/sources.md - If user asks for a starter file quickly, run
scripts/scaffold-clack.sh.
- Build a minimal runnable skeleton first.
- Include imports,
intro(), flow logic, andoutro(). - Add install/run commands for the user's runtime.
- Add prompts with explicit validation and cancellation paths.
- Validate every user-facing field that can fail constraints.
- Handle cancellation after each prompt result with
isCancel(...)andcancel(...).
- Add UX support functions intentionally.
- Use
log.*for structured feedback. - Use
spinner()for long-running single operations. - Use
note()for summaries and next actions.
- For asynchronous multi-step work, use task-oriented patterns.
- Prefer clear status updates and concise task titles.
- Keep success/error messages short and actionable.
- Finalize with a production-ready answer.
- Return complete runnable code (not fragments) unless user asks otherwise.
- Include quick verification steps.
Bundled Resources
-
scripts/scaffold-clack.sh -
Generate a starter CLI from curated templates in JS or TS.
-
Usage:
bash scripts/scaffold-clack.sh <target-dir> [basic|spinner] [js|ts] [auto|npm|pnpm|yarn|bun] -
assets/templates/basic-cli.mjs -
Baseline prompt flow with validation, cancellation handling, and summary note.
-
assets/templates/spinner-cli.mjs -
Prompt flow plus spinner-driven execution pattern for longer operations.
What ships with it
10 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.
- assets/templates/basic-cli.mjs 935 B runs code
- assets/templates/basic-cli.ts 935 B runs code
- assets/templates/spinner-cli.mjs 914 B runs code
- assets/templates/spinner-cli.ts 922 B runs code
- references/best-practices.md 1.3 KB
- references/core-api.md 1.2 KB
- references/examples.md 1.3 KB
- references/prompts-api.md 1.7 KB
- references/sources.md 555 B
- scripts/scaffold-clack.sh 4.0 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.
- 4d ago First seen · 77 lines · 72 tokens per session scan A f348ebf86f4d
clack is a skill published in the GitHub repository pass-agent/loomkin (179 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 696 once invoked, about $0.0004 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
sync-docs
This skill should be used when the user asks to "sync docs", "update guides", "check docs against official", "refresh documentation", "compare guides to official docs", "update docs from upstream", or mentions syncing the SDK documentation guides with the official Claude Agent SDK documentation.
cli-sync
This skill should be used when the user asks to "check CLI schema", "sync CLI version", "check for new CLI options", "update bundled CLI", "compare SDK structs", "check schema drift", "align message structs", "verify CLI compatibility", "check control protocol", or mentions CLI compatibility, schema alignment, or…
elixir
Use when writing or refactoring Elixir/OTP on the BEAM — GenServers, supervision trees and restart strategies, pattern matching, mix projects and releases — or when processes misbehave (restart loops, mailbox growth, call timeouts). NOT a Phoenix web app, LiveView, Ecto or channels (that is phoenix).
phoenix
Use when building an Elixir web app with Phoenix — contexts, Ecto schemas, changesets and migrations, LiveView, channels and PubSub, the generators, and the boundary between domain logic and the web layer. Covers the classic LiveView over-rendering and Ecto N+1 traps. NOT pure OTP work with no web or Ecto layer …
unit-converter
Converts between common units of measurement including temperature, distance, and weight.
code-review
Reviews code changes for quality, security, and best practices.