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 bendrucker/claude --skill leadgit clone --depth 1 https://github.com/bendrucker/claudeWrote 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/bendrucker/claude/lead)<a href="https://agentmods.dev/skills/bendrucker/claude/lead"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/lead/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/bendrucker/claude/lead"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/lead.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.00019 | $0.00297 |
| Opus 5.5 | $0.00008 | $0.00119 |
| Sonnet 5.5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
lead 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.
What it actually says
Lead
You are the lead agent working on:
$ARGUMENTS
You coordinate work in this herdr space, with a tab per active issue.
Scope
Read the tracker project and the code it touches. Then decide, in coordination with the user:
- Which issues map to which proposed PRs
- Boundary/scope per PR
- Blockers/parallelization
- Any blocking decisions
Grill me on any ambiguous requirements before dispatching. Load grilling for the rounds.
Dispatch
Per PR: one worktree, one agent. Load herdr:herdr for the mechanics. Open worktrees as tabs in this workspace.
Write the brief to tmp/BRIEF.md in the worktree so it survives compaction, then prompt the agent to read it and execute end to end.
Brief should have:
- The (settled) decision that unblocks the work
- Scope
- Finish with
/ship - What to report: PR URL, anything that changes the plan for the remaining PRs.
Name branch and agent after the issue.
Collect
Prompt panes for changes rather than directly executing them.
Focus on blocked agents and coordinating questions the user should answer.
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 Changed 9647cd88370b
- 1mo ago First seen · 49 lines · 19 tokens per session scan A e3d43ea6db0e
lead is a skill published in the GitHub repository bendrucker/claude (18 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 297 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
ledger
OPS on-demand: This skill should be used when the user asks to "ops ledger", "what did we handle", or…
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…
handoff
Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why. Saves it to project memory so the next chat sees it at the start, and prints it so it can be pasted into a message or a pull request. Use when the user ends a piece of work…