inbox

inbox is a command for coding agents from punt-labs/beadle. It costs 6 tokens per session (2,216 once invoked), scanned A, original, MIT.

A command for checking an email inbox and optionally setting how often it is checked automatically.

In plain words
What is it for?
Use it to inspect inbox messages, filter results, enable or disable polling, and view the current polling setting.
Why use it?
It saves the steps of reviewing messages and managing the recurring check schedule by hand.

Command

Part of the beadle-dev plugin — 5 commands, 2 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/punt-labs/beadle/inbox
Clone the repo
git clone --depth 1 https://github.com/punt-labs/beadle

Or install beadle-dev, the plugin that ships this one along with the rest of its 5 commands, 2 hooks.

Wrote 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.

agentmods badge for inbox

README.md
[![agentmods](https://agentmods.dev/badge/commands/punt-labs/beadle/inbox.svg)](https://agentmods.dev/commands/punt-labs/beadle/inbox)
Your own site
<a href="https://agentmods.dev/commands/punt-labs/beadle/inbox"><img src="https://agentmods.dev/badge/commands/punt-labs/beadle/inbox.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,216 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.02216
Opus 5 $0.00003 $0.01108
Sonnet 5 $0.00001 $0.00443
Haiku 4.5 $0.00001 $0.00222

Measured 5d ago against content hash 628e84d6728d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

inbox 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 5d 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.

plugin/commands/inbox.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Input

Arguments: $ARGUMENTS

Task

Check beadle's email inbox. You are the beadle — this is your inbox, not the user's.

Argument routing

First, check if the argument matches a polling config command:

  • Exactly one of 1m, 5m, 10m, 15m, 30m, 1h, 2h → set polling interval
  • Exactly n → disable polling
  • Exactly status → show polling config

If none of the above match, treat the argument as a filter (existing behavior).

Polling interval (1m, 5m, 10m, 15m, 30m, 1h, 2h)

  1. Call set_poll_interval with the interval value. If it returns an error, report the error and stop — do not touch the cron job.

  2. Delete every existing /inbox auto-poll cron job (see "Managing the cron job" below). This must happen before creating the new job, so two back-to-back /inbox 10m calls leave exactly one cron job, not two.

  3. Create a new cron job:

    CronCreate(
      cron: "*/10 * * * *",    // from the table below, matching the requested interval
      recurring: true,
      durable: true,           // persists across session restarts
      prompt: "/inbox"
    )
    

    Cron expressions: 1m*/1 * * * *, 5m*/5 * * * *, 10m*/10 * * * *, 15m*/15 * * * *, 30m*/30 * * * *, 1h0 * * * *, 2h0 */2 * * *. All auto-poll jobs must set durable: true — without it, the cron dies on session exit and the autonomous loop silently stops.

  4. Report a single confirmation line combining the set_poll_interval response and the new cron job ID. Example: polling set to 10m; cron job 12c9c370 created (durable, fires */10 * * * *).

Disable polling (n)

  1. Call set_poll_interval with interval: "n". If it returns an error, report the error and stop — do not touch the cron job.
  2. Delete every existing /inbox auto-poll cron job (see "Managing the cron job" below).
  3. Confirm with the set_poll_interval response text.

Read the full file on GitHub · 179 lines

Changes

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.

  1. 5d ago First seen · 179 lines · 6 tokens per session scan A 628e84d6728d

Subscribe to this mod's changes

inbox is a command published in the GitHub repository punt-labs/beadle (3 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 2,216 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-31.