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 agentmods add skills/timdoes/proof-inbox-mcp/proof-inboxnpx skills add timdoes/proof-inbox-mcp --skill proof-inboxgit clone --depth 1 https://github.com/timdoes/proof-inbox-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/timdoes/proof-inbox-mcp/proof-inbox)<a href="https://agentmods.dev/skills/timdoes/proof-inbox-mcp/proof-inbox"><img src="https://agentmods.dev/badge/skills/timdoes/proof-inbox-mcp/proof-inbox.svg" alt="Measured on agentmods" 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.00046 | $0.00388 |
| Opus 5 | $0.00023 | $0.00194 |
| Sonnet 5 | $0.00009 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
proof-inbox 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 5d 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
Proof Inbox
MCP: https://mcp.proofinbox.com/mcp
Auth: workspace_token on the tool call, or Authorization: Bearer <workspace_token>.
Get a token from https://proofinbox.com/buy/verify-500 — it is in the checkout URL.
Reuse it. Never invent a new one.
Grok Bot form: https://proofinbox.com/grok-bot Custom MCP only. Not the Marketplace catalog. Not grok.com/connectors.
Tools
balance— tank check. Costs 0. Call before a batch.verify_email— one address. Fresh checks cost 1. Cache (30 days), syntax errors, and vendor unknown cost 0.receipts— checkout session id and every check. Do not invent session ids.
Loop
- Call
balance. If verify credits are 0, you will need to buy. - On
payment_required, opencheckout_url. Do not invent a URL. - Human approves the checkout charge.
- Poll
balanceevery 2 seconds for about 30 seconds. - Call
verify_emailonce per address. - When asked what the money bought, call
receiptsand show the checkout session id.
Results
status is only valid | invalid | catch_all | unknown.
unknown means the vendor did not finish. That is not valid. Say unknown.
Do not send email. Do not find emails. This product only verifies.
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.
- 5d ago First seen · 41 lines · 46 tokens per session scan A d3315822b43e
proof-inbox is a skill published in the GitHub repository timdoes/proof-inbox-mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 388 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
planning-and-task-breakdown
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.