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 agentmods add skills/flurdy/agent-skills/todaynpx skills add flurdy/agent-skills --skill todaygit clone --depth 1 https://github.com/flurdy/agent-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/flurdy/agent-skills/today)<a href="https://agentmods.dev/skills/flurdy/agent-skills/today"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/today.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.01601 |
| Opus 5 | $0.00017 | $0.00800 |
| Sonnet 5 | $0.00007 | $0.00320 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
today 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 5d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Today — Same-day catch-up
Show what happened today without ending the session or creating a handoff. /today is the
lightweight, anytime complement to /wrap-up: it combines objective activity that may come
from several AI sessions with qualitative context from this conversation only.
When to use
- You want a reminder of today's progress without running the end-of-session workflow.
- Several sessions or repositories may have contributed work today.
- You need a concise status recap with no mutation or required follow-up.
Read-only boundary
Never create or update a handoff. Never change Git state, Beads, Jira, settings, files, or remote state. Do not commit, stash, push, rename or exit the session, update tracker status, or prompt for a mutation. This skill reports evidence only.
Instructions
Re-fetch on every invocation. Run the activity helper in workspace mode:
~/.agents/skills/wrap-up/scripts/activity.sh --workspace
It reuses /wrap-up's local-day filtering and GitHub queries, plus its authoritative
multi-repository resolver. It emits:
---DATE---— local calendar date used by every same-day filter.---WINDOW-START---/---WINDOW-END---— the local, exclusive-end interval applied to commits and Beads records.---SCOPE---—WORKSPACEorCURRENT_REPO.---REPOSITORIES---—{repository}|{absolute_path}for validated repositories.---DIAGNOSTICS---— bounded discovery or member failures.---COMMIT-STATUS---—{repository}|OK|NO_AUTHOR|ERROR.---COMMITS---—{repository}|{worktree}|{branch}|{sha}|{subject}|{when}.---GH-STATUS---,---GH-DIAGNOSTICS---, and the three PR JSON sections used by/wrap-up.---BEADS-STATUS---—{repository}|OK|NO_BD|NO_BEADS_IN_REPO|ERROR.- The three Beads sections —
{repository}|{JSON array}for in-progress, open items created today (BEADS-CREATED-TODAY), and items closed today. The genericBEADS-CREATEDsection includes closed rows for historical consumers; ignore it here.
What ships with it
1 file 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.
- 5d ago First seen · 180 lines · 35 tokens per session scan A a6719d4b69e9
today is a skill published in the GitHub repository flurdy/agent-skills (8 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 1,601 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-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…