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 moose-lab/awesome-workplaces-skills --skill mails-verification-codegit clone --depth 1 https://github.com/moose-lab/awesome-workplaces-skillsWrote 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/moose-lab/awesome-workplaces-skills/mails-verification-code)<a href="https://agentmods.dev/skills/moose-lab/awesome-workplaces-skills/mails-verification-code"><img src="https://agentmods.dev/badge/skills/moose-lab/awesome-workplaces-skills/mails-verification-code.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.00143 | $0.01554 |
| Opus 5 | $0.00072 | $0.00777 |
| Sonnet 5 | $0.00029 | $0.00311 |
| Haiku 4.5 | $0.00014 | $0.00155 |
Grade A, and why
mails 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 7d 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.
curl -X POST https://someservice.com/auth/send-code \ How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mails — Email for AI Agents
Overview
mails gives agents a real @mails.dev mailbox: send, receive, and extract verification codes.
The core agent loop is:
claim mailbox (once) → send email → wait for code → done
Step 1 — Install
npm install -g mails
mails version # should print a version number
Step 2 — Claim a mailbox (one-time, requires human approval)
mails claim <pick-a-name>
With a browser (local machine): browser opens automatically; human approves; CLI saves credentials.
Without a browser (sandbox, SSH, CI — this is the common agent case):
Claiming [email protected]
To complete, ask a human to visit:
https://mails.dev
and enter this code:
KDNR-CHPC
Waiting...
Relay the URL and code to the human. Once confirmed, credentials are saved to ~/.mails/config.json.
Verify setup:
mails config get mailbox # prints your address
mails config get api_key # prints mk_...
Step 3 — The verification code pattern (primary agent use case)
This is the core loop. Long-polls for a code, pipes cleanly to stdout, exits 1 on timeout.
# Basic: wait up to 30s
CODE=$(mails code --to [email protected] --timeout 30)
# In a script — check success before using
if CODE=$(mails code --to [email protected] --timeout 60); then
echo "Got code: $CODE"
else
echo "Timed out — no code arrived"
fi
Trigger the email first (sign-up, login, etc.), then immediately start polling:
# 1. Trigger the email (sign up, request OTP, etc.) — example only
curl -X POST https://someservice.com/auth/send-code \
-d "[email protected]"
# 2. Wait for it
CODE=$(mails code --to [email protected] --timeout 60)
echo "Verification code: $CODE"
Step 4 — Send email
# Basic send (100 free/month included)
mails send --to [email protected] --subject "Hello" --body "World"
# With attachment
mails send --to [email protected] --subject "Report" --body "See attached" --attach report.pdf
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.
- 7d ago First seen · 231 lines · 143 tokens per session scan A 9fdf70521246
mails is a skill published in the GitHub repository moose-lab/awesome-workplaces-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 143 tokens to every session and 1,554 once invoked, about $0.0007 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-31.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.