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 instructions/huacnlee/omamail/agents-mdgit clone --depth 1 https://github.com/huacnlee/omamailWrote 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/instructions/huacnlee/omamail/agents-md)<a href="https://agentmods.dev/instructions/huacnlee/omamail/agents-md"><img src="https://agentmods.dev/badge/instructions/huacnlee/omamail/agents-md.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 | $0.09999 | $0.09999 |
| Opus 5 | $0.04999 | $0.04999 |
| Sonnet 5 | $0.02000 | $0.02000 |
| Haiku 4.5 | $0.01000 | $0.01000 |
Grade A, and why
omamail AGENTS.md scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- The transport is `scripts/mail-transport.sh`, which is curl. Fields cross to How it starts
The opening of the file, as written. The whole thing — 570 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository working agreements
Colors
- Use colors from the active Omarchy system theme. Do not hard-code UI colors.
- Pass semantic colors down from
App.qmlas required component properties so a theme change propagates through every view. - Derive muted, hover, and selected variants from an inherited color with
alpha, or from
Style.normalFillFor/hoverFillFor/selectedFillFor. Do not introduce literal fallback grays. - Secondary text mixes the foreground toward the background, not
Qt.darker. On a light theme, darkening an almost-black foreground makes "secondary" text heavier than body text — the opposite of what it means. tests/test_source.shenforces the no-literal-colors rule. Keep it updated rather than working around it.
Layout
Grouped by module, not by file type. A module holds whatever doing its job
takes — the rules in .js, the object in .qml, side by side. There is no
directory of "all the JavaScript": that arrangement puts a provider's parsing
three directories away from the client that calls it.
| Module | What it is |
|---|---|
| root | Service.qml, BarWidget.qml, App.qml, and nothing else. manifest.json names these three and the shell loads them at that path. |
providers/ |
Everything that differs between mail services: a description per provider, the registry over them, the protocol each speaks, and the pair of objects — signs in, fetches — that each needs. |
account/ |
One mailbox and the list of them. MailAccount.qml, Accounts.js, and the rules in Model.js about what a list does after an action. |
cache/ |
What a query result and a message body are kept in, and the two objects that keep them. |
calendar/ |
The calendars an account serves and their events: the sources in Sources.js, the rules in Calendar.js, the controller that reads and writes them, and the range cache. |
message/ |
A message's own content: parsing it (Message.js) and making it safe to draw (Html.js). |
components/ |
Views. They draw what they are given and decide nothing. |
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.
- today Changed · +76 lines · +1,805 tokens per session bec3f686790e
- 5d ago First seen · 494 lines · 8,194 tokens per session scan A 24772281a34f
omamail AGENTS.md is an instructions file published in the GitHub repository huacnlee/omamail (149 stars, last pushed today), licensed MIT. It adds 9,999 tokens to every session, about $0.0500 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
email-local-mcp CLAUDE.md
Instructions for MarcinWalendowski/email-local-mcp, covering claude.md — email local mcp, naming is enforced, not remembered, gates and releasing.
mail-agent-mcp AGENTS.md
AGENTS.md instructions for SinoEdwards/mail-agent-mcp, covering agents.md, project, entry procedure, security boundaries and architecture.
mail-agent-mcp CLAUDE.md
Claude Code instructions for SinoEdwards/mail-agent-mcp, covering claude.md and claude-specific notes.
mail-time CLAUDE.md
Instructions for veliovgroup/mail-time, covering claude.md, what this repo is, where to look first, mental model for changes and common pitfalls to avoid.
better-email-mcp CLAUDE.md
Claude Code instructions for n24q02m/better-email-mcp, covering claude.md - better-email-mcp, commands, setup, lint & type check and fix.
maket CLAUDE.md
Instructions for ng-galien/maket, covering maket, quickstart, coding principles, dependency injection via awilix — no exceptions and separation of concerns is hard-enforced.