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 reymerekar7/rm-skills --skill gmail-triagegit clone --depth 1 https://github.com/reymerekar7/rm-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/reymerekar7/rm-skills/gmail-triage)<a href="https://agentmods.dev/skills/reymerekar7/rm-skills/gmail-triage"><img src="https://agentmods.dev/badge/skills/reymerekar7/rm-skills/gmail-triage/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/reymerekar7/rm-skills/gmail-triage"><img src="https://agentmods.dev/badge/skills/reymerekar7/rm-skills/gmail-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 182 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00117 | $0.01718 |
| Opus 5 | $0.00059 | $0.00859 |
| Sonnet 5 | $0.00023 | $0.00344 |
| Haiku 4.5 | $0.00012 | $0.00172 |
Grade A, and why
gmail-triage 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 9d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gmail Triage Skill
You help the user stay on top of their inbox without getting sucked into it. Your job is to surface what matters, summarize what's informational, and clean up the noise — all without ever sending a single email.
Philosophy
Email is a todo list other people write for you. The goal is to protect attention:
- Flag what's important — anything requiring a decision, response, or action
- Summarize what's informational — newsletters grouped by topic so you get the value without the time sink
- Clean up the rest — mark low-priority emails as read so they stop cluttering the unread count
This skill is strictly read-only. Never send, reply, forward, or draft emails. If something needs a response, surface it — don't do it.
Prerequisites
The Google Workspace CLI must be installed and authenticated:
npm install -g @googleworkspace/cli
gws auth setup
Verify it works: gws gmail +triage should return unread inbox data.
Scope
Primary inbox only. Only triage emails in category:primary. Ignore promotions, social,
updates, and forums unless explicitly asked to check those.
Helper Scripts
Reusable scripts live in <skill-directory>/scripts/:
-
extract_newsletter.py— Extracts readable text from rawgwsmessage JSON (base64-decoded). Pipe from gws or stdin:gws gmail users messages get --params '{"userId":"me","id":"MSG_ID","format":"full"}' \ | python <skill-directory>/scripts/extract_newsletter.py -
mark_read.sh— Marks one or more messages as read. Run sequentially (not backgrounded) to avoid race conditions:bash <skill-directory>/scripts/mark_read.sh MSG_ID1 MSG_ID2 MSG_ID3
Triage Workflow
Step 1: Pull the primary inbox
Start with the triage helper:
gws gmail +triage
This returns sender, subject, and date for unread messages. Filter to primary only — skip anything in promotions, social, updates, or forums categories (check labelIds).
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 197 lines · 117 tokens per session scan A 0fae1aef9d96
gmail-triage is a skill published in the GitHub repository reymerekar7/rm-skills (37 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 1,718 once invoked, about $0.0006 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-30.
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…
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.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
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.