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/seanmartinsmith/sms-public-mktWrote 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/commands/seanmartinsmith/sms-public-mkt/beads-onboard)<a href="https://agentmods.dev/commands/seanmartinsmith/sms-public-mkt/beads-onboard"><img src="https://agentmods.dev/badge/commands/seanmartinsmith/sms-public-mkt/beads-onboard/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/commands/seanmartinsmith/sms-public-mkt/beads-onboard"><img src="https://agentmods.dev/badge/commands/seanmartinsmith/sms-public-mkt/beads-onboard.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.00043 | $0.00284 |
| Opus 5 | $0.00022 | $0.00142 |
| Sonnet 5 | $0.00009 | $0.00057 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
beads-onboard 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 11d 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
/sms:beads-onboard
Invoke the beads-onboard skill in the current project.
Usage
Run /sms:beads-onboard in any project that has .beads/ initialized (i.e., bd init has been run). The skill walks through an interactive interview (Phase 0 through Phase 6, see the skill's own SKILL.md for the phase definitions) and emits per-project beads conventions.
What this command does
Trigger the beads-onboard skill via the Skill tool. The skill is in this plugin at skills/beads-onboard/SKILL.md.
Prerequisites
- Claude Code with plugin support
bd(beads) CLI version 1.0.4 or later (verify withbd --version)- A git repository
.beads/initialized in the current working directory (bd initalready run)
Implementation
Invoke the Skill tool with skill: "sms:beads-onboard" and pass any arguments through. The skill is self-contained and runs the full interview interactively.
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.
- 11d ago First seen · 28 lines · 43 tokens per session scan A c37483daa1ae
beads-onboard is a command published in the GitHub repository seanmartinsmith/sms-public-mkt (2 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 284 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-31.
Other commands, from other repositories
linear-cleanup
Audit Linear issues for problems (missing labels, stale, duplicates, wrong state, orphaned, unactionable) and propose fixes.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.
linear-curator-run
Run the curator — collect signals from configured signal sources and report.
linear-sync
Populate or refresh the Linear reference files (teams, projects, users, workflows).
linear-search
Search Linear issues by keyword, team, assignee, state, or priority.
linear-my-issues
List Linear issues assigned to you, grouped by state.