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 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/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/flurdy/agent-skills/today"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/today.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Rogue Agent · line 26 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00037 | $0.01956 |
| Opus 5.5 | $0.00015 | $0.00782 |
| Sonnet 5.5 | $0.00007 | $0.00391 |
| Haiku 4.5 | $0.00004 | $0.00196 |
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 4d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Today — Activity recap
The single collection-and-rendering procedure for /today and the /yesterday prompt. The existing
/wrap-up activity helper owns collection; this skill owns report layout and mode rules.
Use it for a catch-up or stand-up recap without ending the session or creating a handoff.
Usage and mode
/today # Same-day catch-up with current-session context
/today --previous-workday # Objective previous-workday recap
/yesterday # Pi/Claude prompt for previous-workday mode
Accept no arguments (same-day mode) or exactly --previous-workday.
Reject unknown arguments and repeated flags before collecting.
The /yesterday prompt prepends --previous-workday and forwards any supplied arguments unchanged
for this validation; never infer the mode from conversation text. Codex uses
/today --previous-workday because this repository does not install prompt templates there.
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, sync, rename or exit the session, transition, comment, update tracker status, or prompt for a mutation. This skill reports evidence only.
Collect once, freshly on every invocation
The helper requires Python 3.10+ for date and JSON processing. Run the installed command for the selected mode once, in the invoking repository or workspace:
| Mode | Command | Report header |
|---|---|---|
| Same-day | ~/.agents/skills/wrap-up/scripts/activity.sh --workspace |
# Today — {DATE} |
| Previous-workday | ~/.agents/skills/wrap-up/scripts/activity.sh --workspace --previous-workday |
# Yesterday — {DATE} |
The helper owns date selection, local-day boundaries, UTC conversion, and validated repository
resolution. Previous-workday means Friday when invoked on Monday and the preceding calendar day
otherwise. Use its ---DATE--- value; never recalculate the date in either entry point.
What ships with it
2 files 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.
- 4d ago Changed b9eff6f1419b
- 28d ago Changed · +2 lines 26e8f71bf2ab
- 1mo ago Changed · -1 lines · +2 tokens per session 63b9df0fd62d
- 1mo ago First seen · 180 lines · 35 tokens per session scan A a6719d4b69e9
today is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 1,956 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…