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/saigonxiii/evc/mondaygit clone --depth 1 https://github.com/SaigonXIII/evcWhat 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.00000 | $0.00807 |
| Opus 5 | $0.00000 | $0.00404 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
monday 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monday
Monday morning startup sequence. Runs multiple commands in order with approval checkpoints, then opens the weekly dashboard.
Trigger
User invokes /monday or says "start the week", "monday morning", "weekly startup"
Sequence
Phase 1: Gather (parallel — no approval needed)
Run these 3 simultaneously using Agent subagents:
Agent 1: Comms Scan
- Run
/project:comms-scan - Scan email + social mentions + project management for anything that came in over the weekend
- Classify into skip / info / meeting / action_required
- Return: action items count, meeting info, unreplied mentions
Agent 2: Performance Review
- Run
/project:performance-review - Pull live social metrics for the last 7 days
- Read last week's output from
{{CONTENT_OUTPUT_DIR}}/[last-week]/ - Read last week's brief from
{{CONTENT_ENGINE_DIR}}/calendar/ - Return: top performer, underperformer, engagement rate, key learning
Agent 3: Intel Scan
- Run
/project:intel-scan - Scan competitors, visual trends, platform updates
- Read
{{CONTENT_ENGINE_DIR}}/memory/competitor-watch.md - Return: top 3-5 actionable insights for this week
Checkpoint 1: Brief the user
Present a combined Monday briefing:
MONDAY BRIEFING — [date]
════════════════════════════════════════
COMMS ([action count] need attention)
[action_required items listed]
[meeting_info items listed]
LAST WEEK PERFORMANCE
Top post: [title] — [engagement rate]%
Impressions: [total] | Eng rate: [rate]%
Key learning: [insight]
INTEL
[top 3 insights]
════════════════════════════════════════
Continue to content planning? (yes/skip)
Wait for user. If "skip" — stop here. If "yes" or similar — continue.
Phase 2: Plan (sequential — needs Phase 1 outputs)
Content Plan
- Run
/project:content-planfor the current week - Feeds in: intel report from Phase 1, performance review from Phase 1
- Produces: week brief + per-day copy drafts + review dashboard
- Present the dashboard link for review
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 · 110 lines · 0 tokens per session scan A 5b57ce4d042e
monday is a command published in the GitHub repository SaigonXIII/evc (56 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 807 tokens. 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-30.
Other commands, from other repositories
weekly-review
Weekly review — read the week's logs, surface patterns, set next week's one priority.
morning-briefing
Recap yesterday, surface priorities, set today's top three.
capture
Capture a raw thought now; triage it to the right place later.
demo-briefing
Run the full morning ritual against the fictional demo/ data — a safe way to see it work, and a safe thing to present from.
end-of-day
Close the day — log what happened, tee up tomorrow.
midday-checkin
Mid-day reset — what's done, what's slipping, what to protect this afternoon.