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 clay-run/agent-plugins --skill workflowsgit clone --depth 1 https://github.com/clay-run/agent-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/clay-run/agent-plugins/workflows)<a href="https://agentmods.dev/skills/clay-run/agent-plugins/workflows"><img src="https://agentmods.dev/badge/skills/clay-run/agent-plugins/workflows/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/clay-run/agent-plugins/workflows"><img src="https://agentmods.dev/badge/skills/clay-run/agent-plugins/workflows.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.00035 | $0.06008 |
| Opus 5 | $0.00017 | $0.03004 |
| Sonnet 5 | $0.00007 | $0.01202 |
| Haiku 4.5 | $0.00003 | $0.00601 |
Grade A, and why
workflows 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
7 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 Changed · +16 lines f32643edc814
- 6d ago First seen · 436 lines · 35 tokens per session scan A bd6084cf9159
workflows is a skill published in the GitHub repository clay-run/agent-plugins (111 stars, last pushed 5d ago), with no licence file. It adds 35 tokens to every session and 6,008 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
pad
Talk to your project. Natural-language project management — create items, check status, plan work, brainstorm ideas, and more.
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
retro
Skill "retro" from AlanHuang168/AI-Project-Workflow, covering goal, use cases, preconditions, required context and inputs.
sync
Promote a change's delta specs into the canonical specs, without archiving. Use when the user wants to update the source-of-truth specs from a change: "sync the specs", "update the canonical specs", "promote the specs". Part of speclaw's lawbook module (draft → build → sync → archive).
loredex-agent-ops
Manage an agent-ops dex — an agency's client fleet (Manager ▸ Client ▸ Pipeline/Agent ▸ Stage). Use when the user wants to add a client, pipeline, agent, or stage; tag clients; generate a client's MCP/plugin tooling from workspace.yml; or check fleet health. Requires a dex created with loredex init --type agent-ops.
loredex-product
Curate the whole product — a cross-project dashboard and brief spanning every project in the dex, with per-project state, the handoff flow between teams, and report-only cross-project risks/duplicates. Use when the user asks for the product view, "where does the whole product stand", "what's the state across…