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 mardab96/b2b-lead-generation-claude-skills --skill spam-folder-checkgit clone --depth 1 https://github.com/mardab96/b2b-lead-generation-claude-skillsWrote 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/mardab96/b2b-lead-generation-claude-skills/spam-folder-check)<a href="https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/spam-folder-check"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/spam-folder-check/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/mardab96/b2b-lead-generation-claude-skills/spam-folder-check"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/spam-folder-check.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.00061 | $0.01276 |
| Opus 5 | $0.00030 | $0.00638 |
| Sonnet 5 | $0.00012 | $0.00255 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
spam-folder-check 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 12d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spam Folder Check
Use this skill when
Someone suspects their emails are not arriving, and nobody has checked.
The tell is almost always the same: reply rates drop, the copy did not change, the list did not change, and the team's first instinct is to rewrite the subject line. Subject lines do not matter to a message that never renders in an inbox.
Run this before anyone rewrites anything.
Do not use it to diagnose weak copy on a campaign that is demonstrably being delivered and opened. That is cold-outbound-sequence-review.
Required input
At minimum, the sending domain. That alone gets you the authentication picture.
Better, add whatever of this exists:
- the DNS TXT records for SPF, DKIM and DMARC, pasted, or permission to read them
- sending volume per day per mailbox, and how long the domain has been sending
- bounce rate, split into hard and soft if the tool reports it
- spam complaint rate
- whether the sending domain is the main company domain or a lookalike bought for outbound
- the sending tool and whether mailbox warmup is switched on
- open rate history, with the caveat below
If someone hands over only a screenshot of a sequence dashboard, say what is missing and check what can be checked.
Analysis workflow
- Run
../scripts/email_auth_check.pyover the records. Counting SPF lookups against the limit of ten, reading the qualifier onall, spotting DKIM test mode and tellingp=nonefromp=rejectare mechanical, and eyeballing them is how a domain passes an inspection and still lands in spam. Pass the records with--spf,--dkimand--dmarc, or a file with one per line. - Read what it returns and say plainly which of the three is missing, misconfigured or merely present but permissive. SPF that ends in
~allwith eleven includes, DKIM that does not verify, and DMARC set top=noneare three different problems with three different fixes. - Check the domain age and reputation posture. A domain that started sending in volume three weeks after registration behaves differently from one sending for four years, and the fix is patience, not configuration.
- Compare volume per mailbox against a conservative ceiling. Most cold outbound problems are volume problems wearing a copy problem's clothes.
- Read the bounce rate as a list-quality signal first and a reputation signal second. A hard bounce rate above a few percent is a list that was never verified, and it damages the domain for months after the campaign ends.
- Read the complaint rate as the strongest available proxy for whether recipients consider this spam. It matters more than any other number here.
- Separate what is broken from what is merely unproven. Open rates cannot confirm delivery. Apple Mail Privacy Protection, on by default since 2021, loads the tracking pixel on delivery whether or not anyone reads the message, so on an Apple-heavy list the number is inflated by an unknown amount. Do not build a delivery conclusion on it.
- Name the one fix that comes first, and say what it will not fix.
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.
- 12d ago First seen · 96 lines · 61 tokens per session scan A c94d42b5cacc
spam-folder-check is a skill published in the GitHub repository mardab96/b2b-lead-generation-claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,276 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…