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 jezweb/vite-flare-starter --skill morning-briefgit clone --depth 1 https://github.com/jezweb/vite-flare-starterWrote 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/jezweb/vite-flare-starter/morning-brief)<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/morning-brief"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/morning-brief/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/jezweb/vite-flare-starter/morning-brief"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/morning-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 47 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00041 | $0.00517 |
| Opus 5 | $0.00020 | $0.00259 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
morning-brief 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 11d 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.
What it actually says
Morning Brief
When to use
- The user asks for a morning brief, daily digest, or summary of the day
- A scheduled task fires (cron-triggered briefing)
Steps
-
Recall context — call
recallandsearch_memoryto pull:- Location (for weather)
- Topics of interest (news filtering)
- Active projects or priorities
- Personal preferences (tone, length)
-
Gather inputs in parallel — these can run independently:
- Weather:
web_searchfor "weather [location] today" or usebrowser_extracton a weather site - News:
web_searchfor top news in saved topics - Calendar/tasks: if a calendar tool is available, query it; otherwise mention "no calendar configured"
- Weather:
-
Compose the brief with this structure:
- Greeting (1 line, time-appropriate: "Good morning, [name]")
- Today's outlook (1-2 sentences: weather, big-picture)
- News highlights (3-5 bullet points with markdown links)
- On your radar (saved priorities, deadlines coming up)
- Suggested focus (1 sentence: what to prioritise today)
-
Render with UI:
- Use
show_metric_cardsfor at-a-glance items (temperature, top story count, deadlines) - Use
show_timelineif the user has scheduled events - Otherwise, plain markdown
- Use
-
Save the brief — call
fs_writeto save tobriefs/YYYY-MM-DD.mdfor later reference.
Style
- Brief and skimmable. Total length 200-400 words max.
- Time-zone aware. Use the user's local time.
- Skip generic greetings ("Hope you have a great day!") — be substantive.
- If something failed (e.g. weather API down), note it briefly and continue.
What not to do
- Don't generate news headlines without searching first (no fabrication)
- Don't include unread emails count without checking — this isn't email triage
- Don't be overly cheerful or motivational
- Don't repeat the same brief format daily — vary the focus based on what's actually changing
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.
- 11d ago First seen · 50 lines · 41 tokens per session scan A 9694837078e0
morning-brief is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 16d ago), licensed MIT. It adds 41 tokens to every session and 517 once invoked, about $0.0002 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.