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/seungyeop-lee/beads-starterWrote 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/seungyeop-lee/beads-starter/beads-starter-always-on)<a href="https://agentmods.dev/plugins/seungyeop-lee/beads-starter/beads-starter-always-on"><img src="https://agentmods.dev/badge/plugins/seungyeop-lee/beads-starter/beads-starter-always-on/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/seungyeop-lee/beads-starter/beads-starter-always-on"><img src="https://agentmods.dev/badge/plugins/seungyeop-lee/beads-starter/beads-starter-always-on.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
beads-starter-always-on 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 yesterday.
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-starter-always-on",
"source": "./",
"version": "0.10.1",
"description": "Always-on beads workflow plugin: the same skills plus a SessionStart hook that applies bds-workflow to every file-modifying task in repositories where bd is initialized",
"skills": [
"./on-demand/skills/"
],
"hooks": {
"SessionStart": [
{
"matcher": "startup|clear|compact",
"hooks": [
{
"type": "command",
"command": "\"${CLAUDE_PLUGIN_ROOT}\"/always-on/hooks/session-start.sh"
}
]
}
]
}
}What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 89 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#beads-starter-always-on 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.
- yesterday First seen · 22 lines scan A 31ece7acadd3
beads-starter-always-on is a plugin published in the GitHub repository seungyeop-lee/beads-starter (1 stars, last pushed yesterday), 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-10-15.
Other plugins, from other repositories
prd-ce
PRD lifecycle methodology engine: scaffolds PRD/SoT/EPICs to template, drives them to completion with stage skills, governs with hooks + deterministic readiness scoring.
tsk-add
Helps Claude queue a development task from the current conversation using tsk add.
github-loop-engineering
Evidence-gated Loop Engineering control loop that uses GitHub Issues and Projects as durable state, evidence, and handoff through the official GitHub MCP Server.
pm-team
A product-management team made up of helpers for clarifying requirements, planning schedules and priorities, and organizing meeting notes.
ai-sdlc-harness marketplace
AI-driven SDLC workflow harness — multi-agent dev with plan → code → review → test → PR.
lanes-bridges
Bridge Lanes with GitHub and Linear: import issues, batch-spawn a session per ticket, and post results back upstream. Split out of lanes-desktop in 0.7.0.