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 leadbay/mcp --skill leadbay_log_outreachgit clone --depth 1 https://github.com/leadbay/mcpWrote 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/leadbay/mcp/leadbay_log_outreach)<a href="https://agentmods.dev/skills/leadbay/mcp/leadbay_log_outreach"><img src="https://agentmods.dev/badge/skills/leadbay/mcp/leadbay_log_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/leadbay/mcp/leadbay_log_outreach"><img src="https://agentmods.dev/badge/skills/leadbay/mcp/leadbay_log_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.00040 | $0.00487 |
| Opus 5 | $0.00020 | $0.00244 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
leadbay_log_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 8d 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
IRON LAW — VERIFICATION REQUIRED. Before calling leadbay_report_outreach, you MUST collect one of: a gmail message id (verification.source = 'gmail_message_id'), a calendar event id (verification.source = 'calendar_event_id'), or a literal one-sentence user confirmation (verification.source = 'user_confirmed', verification.ref = the user's exact words). Skipping or fabricating verification poisons the human team's pipeline.
Log this outreach on Leadbay lead <The lead UUID. Get it from leadbay_pull_leads or leadbay_research_lead_by_id. If not provided in the user's most recent message, ask once before proceeding.>: Summary: <1-2 sentences describing what I did (e.g. 'Sent intro email to CTO citing recent Hornsea contract'). If not provided in the user's most recent message, ask once before proceeding.>
PHASE 1 — COLLECT VERIFICATION (ask the user EXACTLY once)
Before calling leadbay_report_outreach, ask me ONCE which of these applies:
- I sent an email → ask for the Gmail message id (
verification.source = 'gmail_message_id',verification.ref = <the id>). - I booked a meeting → ask for the calendar event id (
verification.source = 'calendar_event_id',verification.ref = <the id>). - Other → ask me for a literal one-sentence confirmation that the outreach happened (
verification.source = 'user_confirmed',verification.ref = my exact words).
PHASE 2 — RECORD
After I answer, call leadbay_report_outreach({lead_id: '<the lead_id (as extracted above)>', note: <summary>, verification: {source, ref}}). Optionally pass dry_run:true first to confirm exactly what would be sent — recommended if I described the outreach but you're not 100% sure how to phrase the note.
PHASE 3 — CONFIRM
Tell me the outreach was logged, name the verification.source used, and surface the response's outreach_id if present so I can refer back to it.
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.
- 8d ago First seen · 27 lines · 40 tokens per session scan A 51fc3ae18ed9
leadbay_log_outreach is a skill published in the GitHub repository leadbay/mcp (0 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 487 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…