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 trevhud/rote --skill skillgit clone --depth 1 https://github.com/trevhud/roteWrote 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/trevhud/rote/skill)<a href="https://agentmods.dev/skills/trevhud/rote/skill"><img src="https://agentmods.dev/badge/skills/trevhud/rote/skill/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/trevhud/rote/skill"><img src="https://agentmods.dev/badge/skills/trevhud/rote/skill.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.01893 |
| Opus 5.5 | $0.00079 | $0.00757 |
| Sonnet 5.5 | $0.00039 | $0.00379 |
| Haiku 4.5 | $0.00020 | $0.00189 |
Grade A, and why
bdr-outreach 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BDR Outreach Campaign
You are a BDR representative. Campaign ideas, theories, and hypotheses go in; a built-out HubSpot sequence comes out.
This skill orchestrates the full outreach pipeline: from identifying target contacts through ZoomInfo or conference lists, to uploading them into HubSpot, running mandatory exclusion checks, crafting personalized email templates, and producing a pre-enrollment report for the BDR to act on.
Phase Routing
Not every invocation requires all phases. Match the user's entry point:
| Entry Point | Start At | Example Triggers |
|---|---|---|
| Full campaign | Phase 1 → 1.5 → 2 | "run an outreach campaign for Orladeyo" |
| Conference list | Phase 2-alt → 4 | "filter this conference list to pharma", "enrich conference attendees" |
| Contacts ready | Phase 4 | "upload contacts to hubspot", "add contacts to list" |
| Exclusion check | Phase 5 | "run exclusion checks", "check do not contact list" |
| Template editing | Phase 6 | "edit sequence template", "create sales template" |
Pipeline
Phase 1: Campaign Brief
Confirm with the user: drug name (brand + generic), condition (full name + acronym), therapeutic area, manufacturer, campaign type (drug-specific, condition-specific, or general-capabilities), and optional job focus.
Phase 1.5: Target Company Research
Read references/target-research.md before starting this phase.
Run external research (Bright Data web search, ClinicalTrials.gov) and internal research (Airweave enterprise search, Salesforce account history, Acme publications) in parallel. Compile a short intel brief covering the company's pipeline in this indication, any existing RWE/HEOR activity, key program names and teams, prior Acme interactions, and validated Acme experience in the TA.
This brief is not a deliverable -- it's working context that directly informs:
- Phase 2: Which titles and program names to search for, and which contacts to keep or discard during vetting
- Phase 6: Specific references to their programs, recent data, and Acme's relevant experience for email personalization
What ships with it
6 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.
- 1mo ago First seen · 164 lines · 197 tokens per session scan A e88181f41be7
bdr-outreach is a skill published in the GitHub repository trevhud/rote (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 197 tokens to every session and 1,893 once invoked, about $0.0008 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
api-interface-design
Use when designing public APIs, module boundaries, provider adapters, tool schemas, or data contracts.
explore
Explore the codebase and summarize how the project is wired.
watch
Open the Roundtable office in the browser — a live, read-only view of this machine's Claude Code sessions, with every subagent as a person at a desk and a timeline you can rewind.
gif
Turn this Claude Code session into a looping timelapse GIF of the Roundtable pixel office — every subagent as a person who walks in, works, reports and leaves. Writes one file in the working directory.
stats
Read every Claude Code transcript on this machine and report what they say about your own fan-out — how much of your output is written inside subagents, what a child costs before it starts, which hooks have ever fired. Read-only.
agent-goal-skill
Take a rough goal description and shape it into a polished, doctrine-compliant agent goal prompt. Output is for the user to copy/paste into Codex, Claude Code (native /goal), Droid, Auggie, or any CLI agent that benefits from a structured goal contract. The skill does NOT execute the goal — it shapes the prompt and…