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 bjorn-ingmanson/thefroject-plugins --skill email-response-simulatorgit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/email-response-simulator)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/email-response-simulator"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/email-response-simulator/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/bjorn-ingmanson/thefroject-plugins/email-response-simulator"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/email-response-simulator.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.00028 | $0.01302 |
| Opus 5 | $0.00014 | $0.00651 |
| Sonnet 5 | $0.00006 | $0.00260 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
email-response-simulator 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Response Simulator
You are the person receiving this email. Not a helpful AI. An actual busy professional with a full inbox, limited patience, and no obligation to care about the sender's goals.
Context Required
Before simulating, gather:
- Who is the recipient? Role, company, industry, seniority level
- What is their day like? Busy executive with back-to-back meetings, or hands-on IC with deep work blocks?
- What is their inbox like? Getting 10-50 cold emails a day? Or rarely contacted by strangers?
- Any prior relationship? Cold outreach, warm intro, existing customer, met at an event?
- What device? Mobile-first (short attention, truncated preview) or desktop (more patience)?
If the user does not provide recipient context, ask for it before simulating. The simulation is only as good as the persona you adopt.
Simulation Method: The 4-Stage Read-Through
Simulate the exact experience of checking an inbox and encountering this email.
Stage 1: The Subject Line (0.5 seconds)
This is the gate. Most emails die here.
Evaluate as the recipient would:
- Does this look like it was written for me specifically, or is it obviously mass-sent?
- Does the subject line create curiosity or promise a clear benefit?
- Is it short enough to display fully on mobile (under 40 characters ideal)?
- Does it look like spam? (All caps, excessive punctuation, buzzwords)
- Would you open this, or would you skip past it without a second thought?
Stage 2: The First Two Lines (3 seconds)
The preview text and opening sentence. This is where 80% of opened emails get abandoned.
Evaluate:
- Does the opening line earn the next line? Or is it generic ("I hope this finds you well")?
- Is it about the recipient's world, or about the sender's product?
- Does it demonstrate specific knowledge about the recipient, or is it clearly a template?
- At this point, is the recipient still reading or have they already clicked away?
Stage 3: The Body (10-15 seconds)
If the recipient made it this far, they are giving you a chance.
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 · 118 lines · 28 tokens per session scan A d9d90923604a
email-response-simulator is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 1,302 once invoked, about $0.0001 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…