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 everway-ai/everway-mcp-server --skill daily-briefinggit clone --depth 1 https://github.com/everway-ai/everway-mcp-serverWrote 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/everway-ai/everway-mcp-server/daily-briefing)<a href="https://agentmods.dev/skills/everway-ai/everway-mcp-server/daily-briefing"><img src="https://agentmods.dev/badge/skills/everway-ai/everway-mcp-server/daily-briefing/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/everway-ai/everway-mcp-server/daily-briefing"><img src="https://agentmods.dev/badge/skills/everway-ai/everway-mcp-server/daily-briefing.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.00114 | $0.00830 |
| Opus 5 | $0.00057 | $0.00415 |
| Sonnet 5 | $0.00023 | $0.00166 |
| Haiku 4.5 | $0.00011 | $0.00083 |
Grade A, and why
daily-briefing 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Briefing
Keywords
what's next, what's my day, brief me, tomorrow's plan, today's plan, what time is my flight, where do I need to be, when is checkout, itinerary for today, rundown, schedule for the 14th
Overview
The moment Everway exists for: standing somewhere with a phone asking "where am I supposed to be next?" This skill answers from the real itinerary — exact times, addresses, and confirmation numbers — rather than from memory.
Use this skill when: the user asks about a specific day or moment on a trip, or wants a walkthrough of what's coming up.
Workflow
Step 1: Resolve trip and day
Call list_trips; if a trip is active today (start ≤ today ≤ end), assume it's that one. Resolve "today"/"tomorrow" against the trip's timezone context — items carry IANA timezone fields, so use the item's local time, not the user's home time.
Step 2: Load and order the day
Call list_itinerary_items, filter to the requested day, and sort by startsAt. Include:
- Items spanning the day (a lodging stay covers every night of its range — mention check-in/check-out only on those days)
- Undated items only if relevant (e.g. a
documentitem holding tickets for that day's activity)
Step 3: Brief, in time order
For each item give what a traveler needs at a glance:
Tuesday, Aug 27 — Tokyo
11:45 Flight — ANA 109 to Tokyo (NH109, conf. ABC123)
Departs Sydney T1 · lands 19:30 local
20:30 Transfer — Airport Limousine Bus to Shinjuku
Conf. LIM-4402
21:15 Check in — Park Hyatt Tokyo
3-7-1-2 Nishishinjuku · conf. PH88231
Nothing after check-in. Tomorrow starts with the 09:00 Tsukiji tour.
Rules:
- Times are the item's local time; say the city or zone when the day crosses zones.
- Always include confirmation numbers when present — that's the check-in desk moment.
- Include addresses for anything the user must physically find.
- Flag tight connections (arrival to next departure under 90 minutes) and end with a one-line pointer to the next morning.
- If asked "what's next" mid-day, give the next upcoming item first, then the rest of the day in brief.
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 · 73 lines · 114 tokens per session scan A 7cf4372c7037
daily-briefing is a skill published in the GitHub repository everway-ai/everway-mcp-server (1 stars, last pushed 1mo ago), licensed MIT. It adds 114 tokens to every session and 830 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…