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.
git clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/eod-review)<a href="https://agentmods.dev/commands/cveralyon/axel-setup/eod-review"><img src="https://agentmods.dev/badge/commands/cveralyon/axel-setup/eod-review.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.1 | $0.00000 | $0.01757 |
| Opus 5 | $0.00000 | $0.00879 |
| Sonnet 5 | $0.00000 | $0.00351 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade A, and why
eod-review 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 8d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EOD Review — End-of-Day team report
Generate an end-of-day report with everything that was done, changed, or moved TODAY. Designed to give non-technical stakeholders (CEO, PM, CS lead) clear visibility into delivery progress without requiring them to read PRs or Linear.
The output is a Slack draft (never a direct send) ready for the user to review and post. When the target channel is mixed (devs + non-devs), a dual layer is produced: non-technical summary on top, optional technical detail below.
Configuration (edit this section for your team)
Before using this skill, edit the YAML block below with your team's channels, repos, and target audience. Sections marked [OPTIONAL] can be deleted if your team does not use that system.
# --- Target channel for the draft (where the report will be posted) ---
target_channel:
name: "#tech-guild" # id: Cxxxxxxx
audience: "mixed" # "mixed" | "technical" | "non-technical"
# --- Slack channels to scan for context on what happened today ---
slack_channels:
- name: "#incidents"
- name: "#tech-guild"
- name: "#clients"
# --- Git repos to scan for "what was done today" ---
git_repos:
- ~/your-org/api-repo
- ~/your-org/frontend-repo
# --- Team member git-email → display-name mapping ---
team_members:
- { email: "[email protected]", name: "You" }
- { email: "[email protected]", name: "Teammate" }
# --- Optional integrations ---
integrations:
linear: true # requires Linear MCP
intercom: false # [OPTIONAL] requires Intercom MCP — client-facing metrics
notion: false # [OPTIONAL] never queried from this command
When to use
- At the end of the workday, before closing
- When your PM/CEO asks "what was done today"
- Before a standup or sync where you need to show daily progress
Data sources (all read-only, all in parallel)
Git (primary source for "what was done today")
For each repo in git_repos:
git fetch origin --prune- PRs merged TODAY by anyone:
gh pr list --state merged --search "merged:>=TODAY" - PRs opened TODAY
- Commits pushed to staging/feature branches TODAY
- Map authors via
team_members(git email → display name)
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.
- 8d ago First seen · 155 lines · 0 tokens per session scan A 9477fbc4e67d
eod-review is a command published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,757 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-31.
Other commands, from other repositories
orc
Parallel multi-agent orchestration for complex features.
parallel-task
Execute bulk modifications across codebase with parallel agents and safety guarantees.
analytics-review
Review analytics and recent commits, then create tasks.
fix-issues
Pick up one approved task, implement the fix, and close it.
add-issue
Help the user create a task for a manually identified item (bug, feature, or improvement).
update-config
Update Dark Flow project settings: language and/or main branch.