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 boshi-xixixi/TraeSkill --skill daily-prepgit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/daily-prep)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/daily-prep"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/daily-prep/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/boshi-xixixi/traeskill/daily-prep"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/daily-prep.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.00059 | $0.02141 |
| Opus 5 | $0.00030 | $0.01071 |
| Sonnet 5 | $0.00012 | $0.00428 |
| Haiku 4.5 | $0.00006 | $0.00214 |
Grade A, and why
daily-prep 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 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.
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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Prep
Generate a structured prep file for the next working day with meeting details, prep bullets, linked tasks, and productivity recommendations.
When to Use
- End of day: "prepare me for tomorrow"
- Any time: "prep me for Friday" or "what does March 25 look like?"
- Weekly planning: run for multiple days
Procedure
1. Determine Target Date
If the user specifies a date, use it. Otherwise, default to tomorrow (current date + 1 day).
If tomorrow is Saturday, default to Monday. If Sunday, default to Monday.
Compute the output path: outputs/YYYY/MM/YYYY-MM-DD-prep.html
2. Pull Calendar via WorkIQ
Use the WorkIQ MCP tool to fetch the calendar. Ask WorkIQ:
"What meetings do I have on {target date}? For each meeting, include: subject, start time, end time, organizer, all attendees with their email addresses, location, whether it's online, and whether I've accepted or declined."
If the response is insufficient, make a follow-up query:
"For the meetings on {target date}, which ones are marked as optional or tentative? Which ones are recurring?"
3. Classify Each Meeting
Apply these labels based on attendee domains and subject:
| Label | Criteria |
|---|---|
[Customer · HIGH] |
External attendees from customer/partner domains, or subject matches a known customer name |
[Internal] |
Only internal company domain attendees |
[Community] |
CoP, community, guild, learning sessions |
[Upskilling] |
Training, workshop, certification, learning |
[Optional · skip] |
Tentative, low importance, or known recurring optional (e.g., "Office Hours", "Open Q&A") |
[Personal] |
Private events, non-work |
Zone Markers
For every meeting, check the organizer field and apply these additional markers:
| Condition | Marker | Action |
|---|---|---|
| Starts ≥ 15:30 and < 16:00 (any organizer) | ⚠️ After-hours |
Recommend decline |
| Starts ≥ 16:00 and not self-organized | ⚠️ After-hours |
Recommend decline |
| Starts ≥ 16:00 and self-organized | (no flag) | OK — you chose to schedule it |
| Before 09:00 and not self-organized | ⚠️ Early |
Recommend decline — intrudes on learning window |
| Before 09:00 and self-organized | (no flag) | OK — you chose to schedule it |
| Overlaps 12:00–13:00 | 🍽️ Lunch conflict |
Note in Calendar Notes |
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 · 156 lines · 59 tokens per session scan A ea2800856b93
daily-prep is a skill published in the GitHub repository boshi-xixixi/TraeSkill (263 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 2,141 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-09-03.
Other skills, from other repositories
vaultr-notes
Guide for working with Vaultr, an AI-native personal note-taking system. Use this skill whenever the user wants to search, find, read, write, save, create, modify, delete, or capture notes — including journal entries, research notes, quick thoughts, knowledge retrieval, or any note-taking task. Trigger when the user…
break-big-questions-into-steps
How to apply Task Decomposition to eliminate context saturation, prevent hallucination cascades, and build complex projects incrementally.
iterate-step-by-step
How to use the 4-Turn Conversational Scaffolding framework to build complex code, strategy, and content incrementally without token exhaustion or quality degradation.
notion
Notion API via curl: pages, databases, blocks, search.
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows. Use when piping output between agents/tools as streaming JSON or building a sequential transform pipeline.
knowledge-discovery
Discover relevant skills and knowledge using tiered approach. SKIP for simple tasks, QUICK for single-skill, STANDARD for multi-skill, DEEP for full feature implementation. Auto-selects tier based on task complexity.