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 voxpelli/claude-beads --skill synergy-trackergit clone --depth 1 https://github.com/voxpelli/claude-beadsWrote 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/voxpelli/claude-beads/synergy-tracker)<a href="https://agentmods.dev/skills/voxpelli/claude-beads/synergy-tracker"><img src="https://agentmods.dev/badge/skills/voxpelli/claude-beads/synergy-tracker/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/voxpelli/claude-beads/synergy-tracker"><img src="https://agentmods.dev/badge/skills/voxpelli/claude-beads/synergy-tracker.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.00197 | $0.11907 |
| Opus 5 | $0.00098 | $0.05953 |
| Sonnet 5 | $0.00039 | $0.02381 |
| Haiku 4.5 | $0.00020 | $0.01191 |
Grade A, and why
synergy-tracker 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 10d 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 — 885 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synergy Tracker
Manage the SYNERGY-*.md files that track shared patterns, divergences,
extraction candidates, and capabilities observed in sibling projects while
building this one. This skill tracks patterns and capabilities across
peer/sibling projects under the same maintainer — not upstream dependency
friction (use /upstream-tracker for that).
Tracking Files
Sibling projects (permanent files)
Sibling projects are declared in .claude/synergy-registry.json (if it exists)
as an array of {name, file, remote, bm-entity, relationship} objects. See
references/synergy-entry-format.md for the full registry schema.
To discover which projects are registered, read .claude/synergy-registry.json
if it exists. If it does not exist, glob for SYNERGY-*.md to infer sibling
names from existing files. If neither is present, ask the user which sibling
project is involved before proceeding.
File naming
Files are named SYNERGY-<project-name>.md. The project name is taken from
the name field in the registry (tier 3 of the canonical derivation
algorithm — synergy-tracker's subject is always sibling). For projects
outside the registry, fall back to tier 4 (directory basename), then
normalize. Full algorithm:
references/project-name-derivation.md. Examples: vp-knowledge →
SYNERGY-vp-knowledge.md, @scope/shared-utils →
SYNERGY-scope--shared-utils.md.
See references/synergy-entry-format.md for the full naming convention
(normalization rules) and references/project-name-derivation.md for the
tiered derivation algorithm shared with /sibling-sync.
Lifecycle
SYNERGY files are permanent — they always exist for registered sibling
projects, even when all sections are empty. When an entry is resolved or
dismissed, remove it and restore the _No entries yet._ placeholder for that
section. Do not delete the file.
Private overlay (PRIVATE-SYNERGY-*.md)
For entries that must stay out of a public repo (a proprietary sibling's
internal paths, client names, unreleased plans), use a gitignored
PRIVATE-SYNERGY-<project-name>.md companion to the committed
SYNERGY-<project-name>.md. It holds additional private entries under the same
four section headings.
What ships with it
3 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.
- 10d ago First seen · 885 lines · 197 tokens per session scan A a602bd864b2a
synergy-tracker is a skill published in the GitHub repository voxpelli/claude-beads (2 stars, last pushed 26d ago), licensed MIT. It adds 197 tokens to every session and 11,907 once invoked, about $0.0010 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 skills, from other repositories
schema-evolve
This skill should be used when the user asks about 'schema drift', 'schema evolution', 'evolve schema', 'schema sync', 'sync schemas', 'update schema fields', 'schema field frequency', 'missing schema fields', 'unused schema fields', 'schema proposal', 'schema cardinality', 'check schema', 'schema audit', 'schema…
knowledge-maintain
This skill should be used when the user asks to fix, repair, or tidy one or more SPECIFIC named notes — 'fix these notes', 'fix the issues in [note]', 'add the missing relations to [note]', 'tidy up [note]', 'fix orphan [note]', 'apply the gardener findings for [note]'. Applies structural fixes (missing sections…
raindrop-triage
This skill should be used when the user asks to 'triage unsorted bookmarks', 'clean up raindrop inbox', 'sort unsorted', 'organize bookmarks', 'raindrop triage', 'process bookmark backlog', 'promote triaged bookmarks', 'classify triaged', 'raindrop cleanup', 'deduplicate bookmarks', 'find duplicate bookmarks', 'tag…
knowledge-garden
This skill should be used when the user asks to audit, health-check, or structurally validate one or more SPECIFIC named notes or a bounded topic cluster — 'audit these notes', 'check this note for orphans or broken links', 'fourth-wall check on [note]', 'validate the structure of [note]', 'spot-check [note]'. Runs a…
nudge
This skill (explicit /nudge only) manages Claude Code feature-adoption nudges sourced from the Basic Memory note main/reference/claude-code-noteworthy-features. Bare /nudge = Mode A (sync): re-read the note, filter out features already marked adopted or declined, and regenerate the tip cache…
session-bookmarks
This skill should be used to save URLs or links found this session as Raindrop bookmarks — triggers: 'bookmark URLs from this session', 'save links we found', 'save notable URLs to Raindrop', 'save session URLs', 'raindrop bookmarks from session'. Scans the current conversation for high-signal URLs discovered during…