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 BreadchainCoop/labor.fun --skill admin-emailgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWrote 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/breadchaincoop/labor.fun/admin-email)<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/admin-email"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/admin-email/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/breadchaincoop/labor.fun/admin-email"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/admin-email.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.00077 | $0.00917 |
| Opus 5.5 | $0.00031 | $0.00367 |
| Sonnet 5.5 | $0.00015 | $0.00183 |
| Haiku 4.5 | $0.00008 | $0.00092 |
Grade A, and why
admin-email 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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Administrative email triage
The org has set an auto-forward rule: administrative mail (grant forms, legal, partnerships, finance) is forwarded to the assistant's own Gmail. Your job is to turn that inbox into tracked, owned work instead of letting it die in someone's personal inbox.
You have the gws Google Workspace tools (mcp__gws__*, gmail included) and
the GitHub MCP (mcp__github__*). Use gws_discover (or the gmail tool's
discovery) to find the exact list / get / modify-labels operations.
Idempotency — read this first
Never create two issues for the same email. The processed-marker is a Gmail
label, triaged:
- Only fetch messages that are in the inbox and NOT labelled
triaged(e.g. a query likein:inbox -label:triaged). - Process each one fully.
- Apply the
triagedlabel (create it if it doesn't exist) — and archive or mark read — the moment you've filed its issue. If you can't apply the label, do NOT file the issue (better to retry next run than double-file).
If there are no untriaged messages, do nothing and wrap any output in
<internal> so the channel stays quiet.
For each new email
- Unwrap the forward. The message is a forward from the admin address — pull out the original sender, subject, date, and body. Quote key specifics (amounts, names, links, dates) rather than paraphrasing them away.
- Classify into one of:
grant-action,legal,partnership,finance,event,other, ornoise.noise= newsletters, receipts, spam, pure FYI with no action — label ittriagedand move on, no issue. - Extract a deadline if the email implies one (form due date, response-by, meeting date). Note it explicitly; the org's deadline reminders pick up issues with due dates.
- Open a GitHub issue (
mcp__github__*) in the repo named in the task prompt:- Title: short and specific, e.g.
Grant action: <funder> application due <date>. - Body: what's needed and by when, the original sender, any links, and a note that it was auto-filed from a forwarded admin email. Do not paste full legal/financial documents — summarize and link.
- Labels: the category (+
admin-email).
- Title: short and specific, e.g.
- Suggest + notify an owner. Pick the most likely owner from the shared-KB
people files (role/skills) or the routing notes in
/workspace/shared-kb/admin-email/config.mdif present.dm_userthem with a one-line heads-up and the issue link. If you genuinely can't tell, leave the issue unassigned and say so in the channel summary so a human routes it. - Mark triaged (step 3 of idempotency).
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.
- 1mo ago First seen · 71 lines · 77 tokens per session scan A 266195b9b5c7
admin-email is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 917 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…