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 bks-lab/open-bridge --skill mail-draftgit clone --depth 1 https://github.com/bks-lab/open-bridgeWrote 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/bks-lab/open-bridge/mail-draft)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/mail-draft"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/mail-draft/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/bks-lab/open-bridge/mail-draft"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/mail-draft.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.00082 | $0.01422 |
| Opus 5.5 | $0.00033 | $0.00569 |
| Sonnet 5.5 | $0.00016 | $0.00284 |
| Haiku 4.5 | $0.00008 | $0.00142 |
Grade A, and why
mail-draft 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 8d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mail-draft
Builds a mail as a DRAFT in the person's mail client. The person reads it and presses Send. There is no send command, not behind a flag, not in any client module: a draft that is wrong costs a minute, a sent mail that is wrong cannot be taken back. "Send X to Y" is a request for the finished draft.
Engine: skills/mail-draft/mail-draft.sh (Python, stdlib + PyYAML). Model and
every field: docs/mail-draft.md.
What decides what
| Question | Answered by | Tier |
|---|---|---|
| Who signs, how to reach them | identity/mail-footers/<id>.yaml (borrows from a persona) |
user / org |
| What occasion, which footer, greeting, attachments | workflow/mail-profiles/<id>.yaml |
user / org |
| Who receives it, in which language, formal or not | identity/mandants/<id>.yaml (mail_profile, defaults.language, defaults.address_form) |
user |
| Colours and type | DESIGN.md through the design theme |
core / fork |
| Machine defaults (client, drafts folder) | bridge-config.yaml mail: |
user |
CORE ships only the engine, the two _schema.yaml and the two _template.yaml.
Every real footer and profile is a USER file (or org when a team shares one
through an overlay), and the schema refuses scope: core for a footer.
Decision tree
Request about mail
├── write / draft / "send" a mail ──────────► § Draft a mail
├── "how will X be addressed?" ─────────────► mail-draft.sh explain --to X
├── new footer / signature / profile ───────► § Set up
├── paste a signature into Outlook/Mail ────► mail-draft.sh signature <footer> --out <dir>
└── "is my mail setup ok?" ─────────────────► mail-draft.sh validate && mail-draft.sh list
Draft a mail
- Resolve the recipient and occasion first:
mail-draft.sh explain --to <who>. It prints the profile, footer, language, form of address and sender, each with the reason. If the profile names astyle_skill, load that skill before writing the text. - Write the body as Markdown into a file (greeting and sign-off come from the
profile; leave them out unless the text needs its own). Syntax: headings,
lists, tables,
> [!NOTE]alerts,[[Button]](url),[done]badges,{{snippet:<name>}}from the profile. - Preview and show the person the text part in chat:
mail-draft.sh preview --to <who> --subject "<s>" --body-file <f> [--attach <file>] - On their go:
mail-draft.sh compose ...with the same arguments. Preflight errors stop it (missing attachment, leftover{placeholder}, required attachment absent). Warnings are printed for the person. - Report what the command printed: client, recipients, attachments, whether the Drafts folder counted it, and for Outlook that "From" must be switched by hand. Never claim a draft that was not verified.
What ships with it
37 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- engine/__init__.py 82 B runs code
- engine/cli.py 14 KB runs code
- engine/clients/__init__.py 2.8 KB runs code
- engine/clients/apple_mail.py 9.8 KB runs code
- engine/clients/outlook.py 6.2 KB runs code
- engine/config.py 3.2 KB runs code
- engine/draft.py 12 KB runs code
- engine/footer.py 23 KB runs code
- engine/lint.py 4.7 KB runs code
- engine/markdown.py 29 KB runs code
- engine/mime.py 1.7 KB runs code
- engine/profiles.py 4.7 KB runs code
- engine/recipients.py 5.7 KB runs code
- engine/theme.py 12 KB runs code
- engine/validate.py 5.2 KB runs code
- mail-draft.sh 2.5 KB runs code
- run-tests.sh 523 B runs code
- scripts/tests/mutate.py 3.2 KB runs code
- tests/__init__.py 0 B runs code
- tests/fixtures/bridge/AGENTS.md 10 B
- tests/fixtures/bridge/cv.pdf 10 B
- tests/fixtures/bridge/DESIGN.md 625 B
- tests/fixtures/bridge/identity/mail-footers/contact.yaml 1.2 KB
- tests/fixtures/bridge/identity/mail-footers/team.yaml 108 B
- tests/fixtures/bridge/identity/mandants/acme.yaml 279 B
- tests/fixtures/bridge/identity/mandants/family.yaml 231 B
- tests/fixtures/bridge/identity/personas/alex.yaml 256 B
- tests/fixtures/bridge/workflow/mail-profiles/application.yaml 545 B
- tests/fixtures/bridge/workflow/mail-profiles/everyday.yaml 376 B
- tests/fixtures/bridge/workflow/mail-profiles/family.yaml 179 B
- tests/mutations.py 14 KB runs code
- tests/support.py 1.4 KB runs code
- tests/test_envelope.py 13 KB runs code
- tests/test_render.py 6.4 KB runs code
- tests/test_review.py 5.4 KB runs code
- tests/test_selection.py 4.8 KB runs code
- tests/test_words.py 3.9 KB runs code
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.
- 8d ago First seen · 109 lines · 82 tokens per session scan A e2f5f24274f4
mail-draft is a skill published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 1,422 once invoked, about $0.0003 per session on Opus 5.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-10-08.
Other skills, from other repositories
slack
Use the assigned Slack bot from Slack conversations, Paperclip tasks, and routines to read shared discussions and collaborate.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.