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/davidroliverba/architectkb/emailnpx skills add DavidROliverBA/ArchitectKB --skill emailgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/email)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/email"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/email.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.00008 | $0.02134 |
| Opus 5 | $0.00004 | $0.01067 |
| Sonnet 5 | $0.00002 | $0.00427 |
| Haiku 4.5 | $0.00001 | $0.00213 |
Grade A, and why
email 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 6d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/email - Email Capture and Draft Skill
Purpose
Capture emails into the vault as structured Email notes, linking them to projects, people, tasks, systems, and data assets. Also supports drafting outbound emails with context from the vault.
Usage
/email # Process email from clipboard/pasted content
/email draft <topic> # Draft a new email using vault context
/email capture # Manually capture and process an email
/email thread <subject> # Find all emails in a conversation thread
Email Direction Types
| Direction | Description | Status Values |
|---|---|---|
inbound |
Email received from someone else | received, processed, archived |
outbound |
Email you sent or plan to send | draft, sent, archived |
draft |
Email being composed (not yet sent) | draft |
Email Purpose Categories (GTD-inspired)
| Purpose | Description | Handling |
|---|---|---|
action-required |
Requires response or action within 2 mins | Process immediately or create Task |
waiting |
Sent request, awaiting response | Track in createdTasks |
fyi |
Informational, no action needed | Archive after reading |
reference |
Important info to keep for future | Store with good keywords |
decision |
Contains or requests a decision | Link to relevant ADR/Project |
Capture Mode (/email or /email capture)
When user pastes email content:
- Extract metadata automatically:
- Subject line
- From (sender email/name)
- To (recipient list)
- CC (if present)
- Date and time
- Thread references (Re:, Fwd:)
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.
- 6d ago First seen · 311 lines · 8 tokens per session scan A 327d3d6a6d82
email is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 2,134 once invoked, about $0.0000 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.