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 vladkesler/initrunner --skill email-triagegit clone --depth 1 https://github.com/vladkesler/initrunnerWrote 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/vladkesler/initrunner/email-triage)<a href="https://agentmods.dev/skills/vladkesler/initrunner/email-triage"><img src="https://agentmods.dev/badge/skills/vladkesler/initrunner/email-triage.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01044 |
| Opus 5 | $0.00028 | $0.00522 |
| Sonnet 5 | $0.00011 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
email-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 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.
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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email triage classification skill.
When to activate
Use this skill when processing a new email that needs to be classified for priority and action required.
Categories
| Category | Action | Slack alert |
|---|---|---|
| URGENT | Needs immediate attention | Individual, immediate |
| REPLY_NEEDED | Requires a response | Individual |
| FYI | Informational, no action | Batch digest (3+) |
| NEWSLETTER | Subscription content | Batch digest (3+) |
| NOTIFICATION | Automated system notice | Batch digest (3+) |
| SPAM | Unwanted, unsolicited | Never |
Methodology
1. Read the email
Read the full message with read_email. Note:
- Subject line
- Sender (From header)
- Recipients (To/Cc -- are you the sole recipient or on a list?)
- Date
- Body content (first 500 chars are most informative)
- Thread indicators (Re:, In-Reply-To header)
2. Check sender profile
Recall the sender from semantic memory:
recall("<sender email> sender_profile")
If a profile exists, use it to inform classification:
- Known high-priority senders shift toward URGENT/REPLY_NEEDED
- Known newsletter senders shortcut to NEWSLETTER
- Known notification senders shortcut to NOTIFICATION
If no profile exists, create one after classification:
remember("<name>, <email>, first seen <date>, context: <topic>",
category="sender_profile")
3. Content analysis
Scan the email body for signal indicators:
URGENT signals:
- Words: urgent, asap, immediately, critical, emergency, deadline, time-sensitive, action required, escalation
- Patterns: short deadline mentions ("by end of day", "within 1 hour")
- Direct address to you with a demand
- High-priority headers (X-Priority: 1)
REPLY_NEEDED signals:
- Direct questions (sentences ending with ?)
- Requests: "can you", "could you", "please", "would you mind"
- Meeting invitations or scheduling requests
- Approval requests
- You are the sole recipient (To, not Cc)
FYI signals:
- Informational tone, no questions or requests
- You are on Cc, not To
- Status updates, announcements
- Shared documents or links for reference
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 · 148 lines · 55 tokens per session scan A d820ae31ee6a
email-triage is a skill published in the GitHub repository vladkesler/initrunner (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 1,044 once invoked, about $0.0003 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
morning-briefing
Compiles a daily morning briefing from active tasks, priorities, and pending items. Use at the start of each working day.
daily-review
End-of-day structured summary and next-session prep. Use at the end of each working day or significant work block.
long-running-task-management
Breaks multi-hour tasks into checkpointed stages with resume capability. Use when a task is expected to take more than 30 minutes or multiple sessions.
cron-management
Skill for reading and writing cron.md in the correct format for scheduled LLM or command tasks. Use when: editing cron.md, adding or changing cron schedules, or removing periodic jobs.
zoom-meeting-scribe
A listen-only note-taking workflow for Zoom meetings. It receives live transcript sections, organizes what was said, and prepares a report after the meeting ends.
notion-tool
Notion integration tool for searching, reading, creating, and updating pages and databases via the API. Use when: editing Notion pages, adding database rows, or searching a workspace.