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.
git clone --depth 1 https://github.com/vinnie357/claude-skillsWrote 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/plugins/vinnie357/claude-skills/beads)<a href="https://agentmods.dev/plugins/vinnie357/claude-skills/beads"><img src="https://agentmods.dev/badge/plugins/vinnie357/claude-skills/beads/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/plugins/vinnie357/claude-skills/beads"><img src="https://agentmods.dev/badge/plugins/vinnie357/claude-skills/beads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
beads 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 2mo 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.
What it actually says
{
"name": "beads",
"version": "0.1.10",
"description": "Beads (bd) distributed git-backed graph issue tracker: task management, dependency tracking, AI agent workflows",
"author": {
"name": "vinnie357"
},
"repository": "https://github.com/vinnie357/claude-skills",
"license": "MIT",
"keywords": [
"beads",
"task-management",
"issue-tracker",
"dependency-tracking"
],
"skills": [
"./skills/beads"
],
"agents": [
"./skills/beads/agents/beads-worker.md"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 agent travel with it, and installing the plugin installs all of them — 69 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2mo ago Changed ef027f391467
- 2mo ago First seen · 23 lines scan A 177060977d69
beads is a plugin published in the GitHub repository vinnie357/claude-skills (27 stars, last pushed 13d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
beads compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| beadsvinnie357/claude-skills | Plugin | 27 | 13d ago | MIT | A | — | Claude Code |
| git-sidebardavila7/claude-code-templates | Plugin | 33k | today | MIT | A | — | Claude Code |
| gittechnicalpickles/pickled-claude-plugins | Plugin | 12 | today | MIT | A | — | Claude Code |
| git-prCasper-Studios/casper-marketplace | Plugin | 15 | 10d ago | MPL-2.0 | A | — | Claude Code |
| digestshdennlin/agent-plugins | Plugin | 3 | 4d ago | MIT | A | — | Claude Code |
| code-qualitydanielbodnar/skills | Plugin | 2 | 3mo ago | MIT | A | — | Claude Code |
| feature-to-pr-factoryaishajv/claude-everything | Plugin | 7 | 13d ago | none | A | — | Claude Code |