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 Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations --skill beads-workflowgit clone --depth 1 https://github.com/Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrationsWrote 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/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/beads-workflow)<a href="https://agentmods.dev/skills/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/beads-workflow"><img src="https://agentmods.dev/badge/skills/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/beads-workflow/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/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/beads-workflow"><img src="https://agentmods.dev/badge/skills/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/beads-workflow.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.02102 |
| Opus 5 | $0.00017 | $0.01051 |
| Sonnet 5 | $0.00007 | $0.00420 |
| Haiku 4.5 | $0.00003 | $0.00210 |
Grade A, and why
beads-workflow 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 8d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 8d ago Changed · -75 lines · -3 tokens per session b2ca0d3a11d7
- 12d ago First seen · 348 lines · 38 tokens per session scan A 339730938c9c
beads-workflow is a skill published in the GitHub repository Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations (73 stars, last pushed 5d ago), with no licence file. It adds 35 tokens to every session and 2,102 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-08-30.
Other skills, from other repositories
loom-usage
Meta-orchestration skill for Claude driving loom itself.
Scaleway Naming And Tagging
Scaleway naming convention and mandatory tags — resource-type abbreviations, region codes, and owner/cost-center/environment/workload tags for cost attribution.
github-triage
Triage GitHub issues through a configurable label-based state machine. Use when user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states. Repo inferred from git remote; all GitHub calls go through gh.
to-issues
Decompose a plan, PRD, or spec into independently-grabbable vertical-slice issues (markdown file by default, GitHub issues via flag). Trigger when the user wants implementation tickets, work decomposition, or to convert an implementation plan into parallelizable work. Takes a plan file and emits atomic vertical slices.
Incident Management
Severity classification, runbook structure, and blameless postmortems — so incidents are handled calmly, restored fast, and learned from.
to-issues
Decompose a plan, PRD, or spec into independently-grabbable vertical-slice issues (markdown file by default, GitHub issues via flag). Trigger when the user wants implementation tickets, work decomposition, or to convert an implementation plan into parallelizable work. Takes a plan file and emits atomic vertical slices.