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 thoreinstein/beads-workflow --skill commitgit clone --depth 1 https://github.com/thoreinstein/beads-workflowWrote 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/thoreinstein/beads-workflow/commit)<a href="https://agentmods.dev/skills/thoreinstein/beads-workflow/commit"><img src="https://agentmods.dev/badge/skills/thoreinstein/beads-workflow/commit/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/thoreinstein/beads-workflow/commit"><img src="https://agentmods.dev/badge/skills/thoreinstein/beads-workflow/commit.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.00023 | $0.01083 |
| Opus 5.5 | $0.00009 | $0.00433 |
| Sonnet 5.5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
commit 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 1mo 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 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.
- 1mo ago First seen · 132 lines · 23 tokens per session scan A 7d56b8c55439
commit is a skill published in the GitHub repository thoreinstein/beads-workflow (11 stars, last pushed 6mo ago), with no licence file. It adds 23 tokens to every session and 1,083 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
commit-staged
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
ox-cli-pr-header
Emit and paste the SageOx credit line at the TOP of a pull-request description — the human-facing counterpart to the machine SageOx-Session: trailer. Run ox pr header at PR-creation time; it renders a thin, on-brand, dark/light-aware single line linking the session(s), plan(s), and discussion(s) that produced the…
document-release
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…
lov-checkpoint-list
A read-only history report built from Git records and project checkpoint logs. A checkpoint is a recorded project milestone or state, while Git is the version-control system that tracks changes and commits.
lov-git-commit-with-context
A Git commit helper that compares the current conversation's intended work with the repository's actual changes before creating a commit. Git is a system for tracking file changes, and a commit records a selected set of those changes.