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 floomhq/moto --skill cold-outreachgit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/cold-outreach)<a href="https://agentmods.dev/skills/floomhq/moto/cold-outreach"><img src="https://agentmods.dev/badge/skills/floomhq/moto/cold-outreach/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/floomhq/moto/cold-outreach"><img src="https://agentmods.dev/badge/skills/floomhq/moto/cold-outreach.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.00077 | $0.00769 |
| Opus 5 | $0.00039 | $0.00385 |
| Sonnet 5 | $0.00015 | $0.00154 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade A, and why
cold-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 9d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Outreach Skill
Core Principles
The test: Would you send this to a friend? If not, it's too salesy.
The goal: Get a response, not make a sale. The first message gets a conversation, not a deal.
The rule: Shorter is always better. If it can be 3 sentences, don't write 6.
The Formula
- Hook (1 sentence): Why you're reaching out. Specific, not generic.
- Relevance (1-2 sentences): Why this is relevant to THEM, not you.
- Ask (1 sentence): One clear, low-friction ask.
Total: 3-4 sentences maximum for the first message.
What Makes a Good Hook
Bad hooks:
- "I hope this message finds you well"
- "I came across your profile and was impressed"
- "I wanted to reach out because..."
Good hooks:
- "Saw your post about [specific thing] - [your reaction or connection]"
- "We just shipped [thing] and thought of you because [specific reason]"
- "You mentioned [specific thing] at [event/interview/post]..."
- "Mutual connection [name] suggested I reach out"
Templates by Use Case
Sales / Partnership Outreach
[Specific hook about their work or company]
[1-2 sentences on why this is relevant to their situation/goals - not what you want]
Would you be open to a 15-minute call this week?
Job / Networking Outreach
[Specific hook about their work or a project of theirs]
[1 sentence on what you're working on / what you're looking for]
Would you be up for a quick call? Happy to keep it to 20 minutes.
Partnership Outreach
[Specific observation about their product/company]
[1-2 sentences on how collaboration could benefit THEM, not you]
Worth a quick chat?
Personalization Checklist
Before sending, verify:
- The hook is specific to THIS person (could not be copy-pasted to 100 others)
- The relevance is about their situation, not yours
- The ask is low-friction (15 min call > 1 hour meeting)
- No "I hope this finds you well" or similar filler
- Under 100 words for the body
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.
- 9d ago First seen · 108 lines · 77 tokens per session scan A 34fe6c3e8168
cold-outreach is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 769 once invoked, about $0.0004 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-30.
Other skills, from other repositories
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
self-assessment
Interactive skill assessment with personalized learning path generation.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
investigate
Systematic root-cause debugging: find the cause before writing any fix.