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/conorbronsdon/agent-workspace/todaynpx skills add conorbronsdon/agent-workspace --skill todaygit clone --depth 1 https://github.com/conorbronsdon/agent-workspaceWrote 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/conorbronsdon/agent-workspace/today)<a href="https://agentmods.dev/skills/conorbronsdon/agent-workspace/today"><img src="https://agentmods.dev/badge/skills/conorbronsdon/agent-workspace/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.00039 | $0.00923 |
| Opus 5 | $0.00019 | $0.00462 |
| Sonnet 5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00092 |
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/today — Morning Heartbeat
A daily check-in that catches staleness, surfaces deadlines, and proposes updates —
including gaps left by sessions that closed without /end. Designed to run in under 60
seconds.
Invocation: user-only (disable-model-invocation: true) — the heartbeat is timed by
you (mornings, or after a gap), and the flag keeps this skill out of ambient context.
Configuration
Read the optional workspace.yaml at the project root. Below, <state_dir>,
<sessions_dir>, and <task_file> are its resolved values; defaults are state/,
sessions/, and TODO.md. Staleness thresholds come from staleness.current_days (3),
weekly_days (5), blockers_days (7). Full reference: docs/state-model.md.
Instructions
-
Establish context. Get today's date. Read
<state_dir>/heartbeat-log.mdto find the last check-in date. -
Scan recent activity. In a git repository, run:
git log --oneline --since="3 days ago"Then check
<sessions_dir>for recent logs. This captures work even from sessions that closed without/end. Outside a git repository, rely on the session logs alone. -
Check state freshness. Same thresholds as
startstep 4 (staleness.*from config). -
Surface deadlines. Read
<task_file>and scan for:- Items with dates in the next 7 days
- Items marked urgent or time-sensitive
-
Age-check open items. Read
<state_dir>/current.mdand check the*(created M/D)*dates on open threads:- Items >7 days old: flag as "stale — still relevant?"
- Items >14 days old: escalate as "likely stale — remove or convert to task?" Present proposals. Do not auto-update.
-
Identify memory gaps. Compare git-log activity against state files:
- Decisions committed but not in
<state_dir>/decisions.md? - Completed work not reflected in
<state_dir>/current.md? List proposed updates. Do not auto-update. Wait for approval.
- Decisions committed but not in
-
Output format:
MORNING CHECK-IN — [DATE] ([day of week]) Last heartbeat: [date] ([N] days ago) SINCE LAST CHECK-IN: - [N] commits: [brief themes] - Session logs: [found/none] STATE: - current.md — [fresh/N days stale] - weekly-priorities.md — [fresh/N days stale] - blockers.md — [fresh/N days stale] DEADLINES (next 7 days): - [items, most urgent first] [If stale items found:] STALE ITEMS: - [item] — [N] days old. [Propose: remove / convert to task] [If memory gaps found:] MEMORY GAPS: - [proposed update]
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 First seen · 98 lines · 39 tokens per session scan A 8012c96c57da
today is a skill published in the GitHub repository conorbronsdon/agent-workspace (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 923 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
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Pinned, always-injected.
Context Doctor
Identify and repair degradation in system prompt, external memory, and skills preventing you from following instructions or remembering information as well as you should.
memanto-companion
Inspect and manage the cross-session engineering memory that Memanto maintains for your Claude Code skills. Use when the user asks what Memanto remembers, wants to see their engineering profile, manually recall context for a skill, or store a decision. The automatic lifecycle hooks handle capture/injection on their…
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.