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/jumplink/postbote/agents-mdgit clone --depth 1 https://github.com/JumpLink/postboteWrote 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/jumplink/postbote/agents-md)<a href="https://agentmods.dev/instructions/jumplink/postbote/agents-md"><img src="https://agentmods.dev/badge/instructions/jumplink/postbote/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.01954 | $0.01954 |
| Opus 5 | $0.00977 | $0.00977 |
| Sonnet 5 | $0.00391 | $0.00391 |
| Haiku 4.5 | $0.00195 | $0.00195 |
Grade A, and why
postbote AGENTS.md 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — postbote
Operating guide for AI agents in the postbote repo. Follows the agents.md convention; the human overview is README.md. This repo is a submodule of werkstatt, whose AGENTS.md carries the broader workspace rules — this file is the postbote-specific layer and wins where they differ.
The directory is
projects/mail, the repo ispostbote. That is deliberate — do not "fix" it. Git keys submodules by path, not by repo name, and werkstatt already carries three such pairs (projects/das-frittier-werk,projects/jumplink,projects/riba).
What this is
Mail (IMAP), contacts (CardDAV) and calendar (CalDAV) through GNOME Online Accounts, as a
CLI and an MCP server. A TypeScript monorepo that runs on GJS via gjsify (not Node),
following the buchhaltung/leitstand pattern: pure-TS packages/* + one app workspace that
carries the gjsify toolchain and picks a frontend at the yargs entrypoint.
The code came out of buchhaltung/packages/gnome; the git history there is the deeper record.
v1 is read-only. IMAP is spoken with BODY.PEEK only, so \Seen is never set. There is no
SMTP, no flag write, no move, no delete.
Package layout — and the one rule that holds it together
| Package | Contains | May import |
|---|---|---|
@postbote/protocol |
Pure. RFC grammar (IMAP lexer, ENVELOPE, FETCH, LIST, BODYSTRUCTURE, MIME, RFC 2047/2231, modified UTF-7), DTOs, errors, the MailBackend port |
nothing |
@postbote/gnome |
GOA + EDS: accounts, contacts, calendar, IMAP credentials | protocol, gi:// |
@postbote/imap |
Gio TLS transport, IMAP client, folders, search, fetch, attachments | protocol, gnome, gi:// |
@postbote/store |
SQLite index, sync engine, XDG paths, file writes | protocol, node:* |
postbote-cli (app/) |
yargs CLI + MCP server | all of the above |
store must never import imap. The sync engine is driven through the MailBackend port
declared in protocol and injected by app. That keeps store free of gi:// even
transitively, which is the only reason the sync algorithm — the most intricate part of this
project — can be unit-tested on Node against a fake backend and :memory:. If you find
yourself wanting to import imap from store, add a method to the port instead.
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.
- 2d ago First seen · 120 lines · 1,954 tokens per session scan A a413911be7ff
postbote AGENTS.md is an instructions file published in the GitHub repository JumpLink/postbote (0 stars, last pushed 25d ago), licensed MIT. It adds 1,954 tokens to every session, about $0.0098 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.