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/fridaygit 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.00891 |
| Opus 5 | $0.00000 | $0.00445 |
| Sonnet 5 | $0.00000 | $0.00178 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
friday 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 2d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Friday
End-of-week close-out. Reviews performance, digests team progress, cleans up project management, and saves session state.
Trigger
User invokes /friday or says "close out the week", "friday wrap", "end of week"
Sequence
Phase 1: Review (parallel)
Run these 2 simultaneously using Agent subagents:
Agent 1: Performance Review
- Run
/project:performance-review - Pull live social metrics for the last 7 days
- Read this week's content output and brief
- Compare execution vs plan
- Rank posts by engagement
- Write
[week]-review.mdto{{CONTENT_ENGINE_DIR}}/calendar/ - Return: top post, underperformer, key learning, narrative recommendation
Agent 2: Weekly Digest (if PM tool configured)
- Aggregate project management state across all teams
- Read team channels if accessible
- Return: per-department progress, blockers, completion rates
Checkpoint: Present the review
FRIDAY REVIEW — W[N]
════════════════════════════════════════
CONTENT PERFORMANCE
Posts published: [count]/[planned]
Total impressions: [number]
Engagement rate: [rate]%
Top post: [title] — [rate]%
Key learning: [insight]
Next week recommendation: [direction]
TEAM PROGRESS
[department summaries]
Blockers: [list or "none"]
════════════════════════════════════════
Anything to add or correct before closing?
Wait for user input. Incorporate any corrections.
Phase 2: Close out (sequential)
Step 1: Update project management
- Check for open issues due this week
- Flag any that are overdue
- Move completed items to Done if not already
- Report: [count] closed, [count] overdue, [count] carried to next week
Step 2: Update memory
- Append performance findings to
{{CONTENT_ENGINE_DIR}}/memory/learning-log.md - Update visual performance log if applicable
- Update asset library with any new assets produced this week
Step 3: Capture lessons
- Run
/project:lesson-capturewith this week's key learnings - Auto-capture any QA failures from this week (auto-lesson feature)
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.
- 2d ago First seen · 121 lines · 0 tokens per session scan A 547b80f74d17
friday 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 891 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
review-tool
Research a tool or product for skill-gap, architecture, and verb-fit per the Anatomy framework.
setup
First-run setup — replace the fictional company and authors with yours.
review-content
Review content for brand alignment, lead placement, bio consistency, and proof points.
voice-check
Check a draft against the author's voice profile and flag deviations.
content-status
Scan all content directories and report status of drafts, ideas, and published content.
draft-blog
Scaffold a blog post with proper structure, voice, and frontmatter.