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 commands/parkerm2/create-claude-workflow/start-daygit clone --depth 1 https://github.com/ParkerM2/create-claude-workflowWrote 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/commands/parkerm2/create-claude-workflow/start-day)<a href="https://agentmods.dev/commands/parkerm2/create-claude-workflow/start-day"><img src="https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/start-day.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.00050 | $0.04675 |
| Opus 5 | $0.00025 | $0.02337 |
| Sonnet 5 | $0.00010 | $0.00935 |
| Haiku 4.5 | $0.00005 | $0.00468 |
Grade A, and why
start-day 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 3d 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 — 665 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/start-day
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Get a comprehensive morning briefing: what you shipped yesterday, what you missed overnight, what's due today, and how to prioritize it all.
Usage
/start-day # Standard briefing
/start-day --force-refresh # Bypass cache, pull fresh data from all sources
/start-day --skip-setup # Skip first-run config if no memory exists
How It Works
┌────────────────────────────────────────────────────────────────┐
│ /START-DAY BRIEFING │
├────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Git log to find yesterday's commits │
│ ✓ Load tasks from TASKS.md │
│ ✓ Recent progress files │
├────────────────────────────────────────────────────────────────┤
│ ENHANCED (with task tracker) │
│ + Current sprint tickets with descriptions │
│ + Assigned comments/mentions in Jira │
│ + Status changes by others overnight │
├────────────────────────────────────────────────────────────────┤
│ PREMIUM (with all tools) │
│ + Slack: Mentions, DMs, high-priority channel messages │
│ + GitHub: PR reviews, CI failures, new comments │
│ + Jira: Blockers, dependency updates, team activity │
└────────────────────────────────────────────────────────────────┘
The Briefing (in order)
1. End-of-Day Recap (What You Shipped)
Summary of yesterday's work:
- Latest commits from git log
- Tasks marked complete in TASKS.md
- Activity from Jira (issues closed, PRs merged)
- Files modified (from git)
2. Missed Notifications (What Needs Your Attention)
Overnight activity prioritized by urgency:
- 🔴 Blockers: Issues blocking your work, dependencies you own marked blocker
- 🟠 Mentions: Slack/Jira mentions, direct messages, tags in comments
- 🟡 Status Changes: Tickets assigned to you that changed status (not by you)
- 🔵 Requests: PR reviews waiting, code comments needing response
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.
- 3d ago First seen · 665 lines · 50 tokens per session scan A 56bdcf21244d
start-day is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 4,675 once invoked, about $0.0003 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.