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 seanmartinsmith/sms-public-mkt --skill beads-onboardgit 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/skills/seanmartinsmith/sms-public-mkt/beads-onboard)<a href="https://agentmods.dev/skills/seanmartinsmith/sms-public-mkt/beads-onboard"><img src="https://agentmods.dev/badge/skills/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/skills/seanmartinsmith/sms-public-mkt/beads-onboard"><img src="https://agentmods.dev/badge/skills/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.00096 | $0.10703 |
| Opus 5.5 | $0.00038 | $0.04281 |
| Sonnet 5.5 | $0.00019 | $0.02141 |
| Haiku 4.5 | $0.00010 | $0.01070 |
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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads Onboard
Set up project-specific quality conventions for beads through an interactive interview. Analyze the codebase, ask targeted questions, and generate convention files plus inline integration content (in AGENTS.md or CLAUDE.md, per user choice) that make agents produce high-quality, searchable, non-redundant beads — without needing to read a separate conventions file before every action.
Run once per project, or re-run to upgrade conventions with improved guidance. Always offers a review pass on re-run.
Onboard version: v0.3.0
Surface: inline integration block (AGENTS.md or CLAUDE.md, user-chosen) with translation matrix and load-bearing rules. Multi-axis labels: area:* + view:* sub-areas + cross-cutting (concern:*, platform:*, workflow:*) + universal mode:* workflow-mode + conditional contrib:*. Dolt-primary PRIME.md preamble with explicit sync, search, notes and cross-project rules, under a size budget. Starter formula. Pre-seeded bd remember entries. --parent alone for new children of an epic. labels.md carries explicit multi-area composition patterns. bd lint surfaced as a named quality-gate primitive (auto-lint at create + corpus audit).
Bootstrap: Phase 0 auto-bridges bd init with detection-aware flags. Backwards-compat snapshot when upgrading across major versions. Global PRIME.md carries a version marker with a five-branch path (regenerate / review / upgrade / upgrade-from-unknown / foreign). Platform-aware config paths (Linux / macOS / Windows).
Self-detection (Phase 4): verb-level (5a), flag-level (5b) and mutual-exclusion (5c) bd CLI surface checks; internal version-string drift check (known-targets + unknown-position sweep); bd init .gitignore leak warning when --setup-exclude is in use; starter-formula parse check.
v0.3.0 (2026-10-09): bd 1.3.0 alignment; requires bd 1.3.0 or later. (1) The generated PRIME files and integration block state bd's working rules in full, self-contained: beads and code sync on separate channels (git push never ships bead data), explicit session close (bd sync, then git pull --rebase && git push), consent-gated adoption of git origin as the Dolt remote (never a public repo), consented schema migrations with one designated migrator, title-and-ID-only bd search, --notes replaces while --append-notes appends, cross-project filing with bd -C. (2) Corrected statements that are false at bd 1.3.0: labels hold state and bd set-state adds an event bead (the events table is per-machine); actor chain is --actor → $BEADS_ACTOR → git user.name → $USER; timer gates take --timeout, not the nonexistent --until (calendar dates go through bd defer --until); bd dolt fetch removed; new child of an epic is --parent alone, since bd rejects --id + --parent. New matrix rows for bd defer, bd state list, bd history --events, bd conflicts, bd recompute-blocked, gate create --title. (3) Size budgets: global and per-project PRIME under 6,000 characters each, and the per-project PRIME does not restate the integration target file. (4) Global PRIME gains a foreign branch for markers with a newer major (a stale install no longer overwrites a newer global silently); markers now carry source: sms:beads-onboard. (5) File 7 adds bd 1.3.0's *.gate.lock* root rule; File 9 starter formulas rewritten in the format bd 1.3.0 parses, with a bd formula show check. (6) Phase 4 adds the mutual-exclusion check (5c) and tracks bd 1.3.0's global flags. Re-onboard offers the standard review pass.
v0.2.0 (2026-05-21): Three onboard improvements. (1) Phase 0 global PRIME.md detection enumerates Linux/macOS/Windows config-dir paths explicitly (confirmed via bd source's os.UserConfigDir() resolution: ~/.config/beads/ on Linux respecting $XDG_CONFIG_HOME, ~/Library/Application Support/beads/ on macOS, %APPDATA%\beads\ on Windows). (2) New Q8: Integration Target lets users choose where the beads integration block lives — AGENTS.md (tool-agnostic, default for multi-tool setups) or CLAUDE.md directly (for Claude-Code-only users); Phase 0 detection (claude_md_substantial, agents_md_has_content) drives the default, Phase 3 generation branches on the answer, and Phase 4 step 9 migration recommendation becomes contextual (only fires on Option A + substantial CLAUDE.md). (3) New Q9: Lint at Create Time wires bd lint as a per-project quality gate via bd config set validation.on-create warn; Phase 0 step 8 detects the current setting, the Phase 3 post-table step applies it on opt-in, File 5 gains a "Quality gates" callout, File 4 gains a "Lint at create time" section, and Phase 4 step 8 always recommends a one-time bd lint corpus sweep regardless of Q9 answer.
What ships with it
4 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.
- 19d ago Changed · +25 lines a87b9ea959c9
- 2mo ago First seen · 342 lines · 96 tokens per session scan A bd6b2d59456b
beads-onboard is a skill published in the GitHub repository seanmartinsmith/sms-public-mkt (3 stars, last pushed 21d ago), licensed MIT. It adds 96 tokens to every session and 10,703 once invoked, about $0.0004 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
project-init
Use when beads/Dolt database initialization fails, when bd commands return errors about missing databases, when setting up beads in a new project, or when recovering from diverged Dolt history. Handles fresh init, bootstrap from remote, and recovery workflows.
project-update
Update project configuration to match the latest HCF plugin defaults. Use when the HCF plugin has been updated and you want to sync your project's config.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
write-documentation
Use when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read. Not for code comments, commit messages, or agent-to-agent communication.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
research-driven-development
Use when the user asks a question about a topic, requests research, or when understanding something is needed before planning. Triggers on "research this", "what is X", "how does Y work", "compare A vs B", "investigate", "deep dive", "look into".