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_extend_my_lensgit 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_extend_my_lens)<a href="https://agentmods.dev/skills/leadbay/mcp/leadbay_extend_my_lens"><img src="https://agentmods.dev/badge/skills/leadbay/mcp/leadbay_extend_my_lens/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_extend_my_lens"><img src="https://agentmods.dev/badge/skills/leadbay/mcp/leadbay_extend_my_lens.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.00058 | $0.01000 |
| Opus 5 | $0.00029 | $0.00500 |
| Sonnet 5 | $0.00012 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
leadbay_extend_my_lens 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user wants more leads on the current lens — a bigger batch than what the standard daily fill delivers. Execute the extend flow end-to-end.
GATE — DEFER TO TOOL RENDERING. When you call a Leadbay composite that ships its own RENDERING block (every composite in 0.9.0+ does), render the response using that block's recipe verbatim — score bars, glyph palette, column order, hide-list, link priorities, all of it. Do NOT substitute prose, a numbered list, or a different column structure even when an orchestrating prompt's body suggests alternate framing. Prompt-specific commentary (motivational nudges, summaries, next-action recommendations) belongs ABOVE or BELOW the canonical table, never in place of it.
If the prompt's body and the tool's RENDERING appear to conflict, the tool's RENDERING wins for the structural layout; the prompt's voice wins for the commentary that surrounds it.
PHASE 1 — PRE-CHECK QUOTA
Call leadbay_account_status and find the LENS_EXTRA_REFILL entry — in quota.org.resources[] first, falling back to quota.user.resources[] when quota.org is absent (non-admin callers only get the user group), matching the type case-insensitively (LENS_EXTRA_REFILL / lens_extra_refill). If count is at/over the daily cap and extra_count (when provided) wouldn't fit, skip PHASE 2 and surface the three options via your host's choice widget (ask_user_input_v0 or AskUserQuestion) now: smaller count / wait until resets_at / upgrade plan. Don't waste a write call you already know will 429.
PHASE 2 — PICK SEEDS SILENTLY
IRON LAW — DO NOT SHOW THE SEED CANDIDATES TO THE USER. They asked for more leads, not a candidate review. The seed list is internal scaffolding.
Call leadbay_seed_candidates (defaults to last-active lens). Pick 3–5 seeds using this priority order:
- Engagement (load-bearing) —
liked: true, then highorg_contacts_count + prospecting_actions_count. The user already validated these. qq_answers— pick candidates whose qualification answers align with the target profile.tags— purchase-intent alignment.sector / size_min / size_max— shape similarity.ai_agent_score— overall AI fit (tie-breaker).
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 · 49 lines · 58 tokens per session scan A ddabbc649404
leadbay_extend_my_lens is a skill published in the GitHub repository leadbay/mcp (0 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,000 once invoked, about $0.0003 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…