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 floomhq/moto --skill email-checkgit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/email-check)<a href="https://agentmods.dev/skills/floomhq/moto/email-check"><img src="https://agentmods.dev/badge/skills/floomhq/moto/email-check.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.00053 | $0.00622 |
| Opus 5 | $0.00026 | $0.00311 |
| Sonnet 5 | $0.00011 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
email-check 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
status, data = mail.fetch(mid, "(BODY.PEEK[HEADER.FIELDS (FROM SUBJECT DATE)])") How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Check Skill
CRITICAL: Preserve Read/Unread Status
Users often use UNREAD status to track items. NEVER mark emails as read.
- Use
BODY.PEEK[]NOTRFC822(RFC822 marks as read) - If accidentally marked read:
mail.store(num, '-FLAGS', '\\Seen')
How to check emails
Use Python with imaplib. Always use BODY.PEEK[] for fetching.
import imaplib
import email
from email.header import decode_header
def check_inbox(server, email_addr, password, folder="INBOX", unseen_only=True, limit=10):
mail = imaplib.IMAP4_SSL(server)
mail.login(email_addr, password)
mail.select(folder, readonly=True) # readonly=True as extra safety
criteria = "UNSEEN" if unseen_only else "ALL"
status, messages = mail.search(None, criteria)
msg_ids = messages[0].split()[-limit:] if messages[0] else []
results = []
for mid in msg_ids:
# CRITICAL: BODY.PEEK not RFC822
status, data = mail.fetch(mid, "(BODY.PEEK[HEADER.FIELDS (FROM SUBJECT DATE)])")
header = email.message_from_bytes(data[0][1])
subject = decode_header(header.get("Subject", ""))[0][0]
if isinstance(subject, bytes):
subject = subject.decode(errors="replace")
results.append({
"from": header.get("From", ""),
"subject": subject,
"date": header.get("Date", "")
})
mail.logout()
return results
Common tasks
Check for unread messages
Loop through configured accounts, report unread count and latest subjects per account.
Search for email from specific sender
mail.search(None, 'FROM "[email protected]"')
Search by subject
mail.search(None, 'SUBJECT "keyword"')
Check specific folder
Gmail labels map to IMAP folders: [Gmail]/Sent Mail, [Gmail]/Drafts, [Gmail]/Spam
Date range search
mail.search(None, 'SINCE "01-Mar-2026" BEFORE "08-Mar-2026"')
Setup
Configure your accounts in environment variables or a config file:
IMAP_SERVER=imap.gmail.com
[email protected]
IMAP_PASSWORD=your-app-password
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 · 87 lines · 53 tokens per session scan A f24c712e7831
email-check is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 622 once invoked, about $0.0003 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 skills, from other repositories
rtk-optimizer
Wrap high-verbosity shell commands with RTK to reduce token consumption. Use when running git log, git diff, cargo test, pytest, or other verbose CLI output that wastes context window tokens.
session-save
Save the current session state (decisions, modified files, current status, and next steps) to a handoff file for later resume.
handoff-create
Generate a structured handoff document from the current session. Captures scope, relevant files with line numbers, key discoveries, work completed, current status, next steps, and code snippets. Use before ending a session or handing work to another agent.
handoff-update
Update an existing handoff document with current session progress. Applies section-specific merge rules: append-only for Work Done (never deletes history), replace for Status and Next Steps, merge for Files and Discoveries. Falls back to creating a new handoff if no source file is found.
handoff-resume
Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then confirms understanding before proceeding.
session
Session lifecycle management. Parent skill for session-related skills: learning (pattern extraction) and compact (context compression).