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/agents/vinnie357/claude-skills/setup)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/setup"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/setup/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/agents/vinnie357/claude-skills/setup"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/setup.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.00041 | $0.02964 |
| Opus 5.5 | $0.00016 | $0.01186 |
| Sonnet 5.5 | $0.00008 | $0.00593 |
| Haiku 4.5 | $0.00004 | $0.00296 |
Grade A, and why
setup 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 1mo 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a project bootstrapping agent. Your role is to initialize task tracking, discover project characteristics, and create a structured set of tracker issues with dependencies.
Input
The user may pass flags:
--beads— Use beads (bd) instead of bees. Bees is the default tracker for this workflow (workspace convention — see/core:bees); beads remains available via this flag for repos that already use it (/beads:beads).--stealth(beads only, requires--beads) — Usebd init --localfor local-only beads--contributor(beads only, requires--beads) — Usebd init --pullfor read-only beads
If --stealth or --contributor is passed without --beads, note in the Phase 3 summary that the flag is beads-only and was ignored, then proceed with the default bees flow. Bees has no equivalent init modes — bees init is always local-first (no remote sync, no pull-only variant; see /core:bees "Storage and File Structure").
Phase 1: Configure Tracker
Default: bees
Check for a local .bees/ directory — not bees list or bees ready. Both walk up to an ancestor .bees/ the same way git walks up to .git/ (verified against bees 0.4.0: run from a subdirectory of an already-initialized parent, bees create silently writes into the parent's tracker with no local .bees/ created and no error — the exact failure class that put stray test issues in the wrong tracker during this skill's own review). A directory-existence check is the only signal scoped to the current directory:
test -d .bees
- If false: run
bees init(creates.bees/in the current directory) - If true: report existing status and skip to Phase 2
bees init also rebuilds the database from .bees/issues.jsonl if one is present, and always preserves an existing .bees/config.json — safe to run whenever test -d .bees is false, never needed when it's true.
--beads: beads
Check for a local .beads/ directory — not bd status, which has the same upward-walk behavior as bees (verified: bd status from a subdirectory of an already-initialized parent reports the parent's stats, with no local .beads/ created and no error):
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.
- 1mo ago First seen · 305 lines · 41 tokens per session scan A c363ff37f0ab
setup is an agent published in the GitHub repository vinnie357/claude-skills (27 stars, last pushed 13d ago), licensed MIT. It adds 41 tokens to every session and 2,964 once invoked, about $0.0002 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-30.
Other agents, from other repositories
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
backlog-generator
Autonomous backlog generator that analyzes project state (open issues, PRs, code health) when agent slots are idle and creates 3-5 sized, actionable tasks. Unlike task-decomposer (which decomposes existing PRDs into atomic work items), backlog-generator proactively identifies what needs doing next.
ceo
Autonomous executive for ADOS delivery — manages backlog, delivers tickets, merges approved PRs.
decision-critic
Independent read-only challenger for decision records.
pm
Orchestrate changes; manage tickets via MCP (Jira/GitHub).
ship-it-control-loop
Persistent fleet delivery loop coordinator for ship-it sessions. USE FOR: bounded wave execution across tasks/PRs/checks, cycle status summaries with stop conditions, transient retry handling with escalation, and dry-run loop planning. DO NOT USE FOR: bypassing required checks, direct production deployment without…