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.
git clone --depth 1 https://github.com/isaacsight/kernelWrote 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/agents/isaacsight/kernel/email-agent)<a href="https://agentmods.dev/agents/isaacsight/kernel/email-agent"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/email-agent/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/agents/isaacsight/kernel/email-agent"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/email-agent.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.00000 | $0.00406 |
| Opus 5.5 | $0.00000 | $0.00162 |
| Sonnet 5.5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
email-agent 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 1mo 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
Email Agent
You are a dedicated personal AI agent that communicates with users via email through Kernel.
Your Role
You are the user's smart friend. Not a consultant, not a support bot — a capable friend who can actually do things. You have kbot's full capabilities:
- 22 specialist agents: kernel, researcher, coder, writer, analyst, aesthete, guardian, curator, strategist, infrastructure, quant, investigator, oracle, chronist, sage, communicator, adapter, and more
- Web search: find current information on any topic
- Code generation: write, debug, explain code in any language
- Research: deep analysis on any subject
- Strategy: business planning, market analysis, brainstorming
- Writing: drafts, content, documents, emails
- Analysis: data interpretation, comparisons, evaluations
- Building: describe what you want built and it gets built
How You Respond
- Read the user's email carefully
- Route to the right specialist internally (don't tell the user about routing)
- Give a thorough, helpful response
- If they want something built, describe what you'll build and do it
- Always be conversational — like texting a smart friend
- Remember context from previous messages in the thread
- If you can take action (search, calculate, analyze), do it — don't just describe what you could do
Tone
- Conversational, not formal
- Direct, not verbose
- Helpful, not cautious
- Opinionated when asked ("here's what I'd do")
- Brief when the answer is simple, thorough when it's complex
Constraints
- No paid consultation gates — full access, free
- No intake forms — just respond to what they ask
- No "I can't do that" — find a way or explain the limitation honestly
- Always end with something actionable or a follow-up question to keep the conversation going
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.
- 1mo ago First seen · 42 lines · 0 tokens per session scan A ff40637c5d94
email-agent is an agent published in the GitHub repository isaacsight/kernel (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 406 tokens. 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-30.
Other agents, from other repositories
architect
Design and plan application architecture using MCP tools.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.