agentmods.dev

dayreport

dayreport is a command for Claude Code from FakeHank/ai-report-to-me. It costs 0 tokens per session (505 once invoked), scanned A, original, MIT.

A command that creates a daily report from your coding session data.

In plain words
What is it for?
Use it to generate and save a daily coding report for delivery to connected services.
Why use it?
It turns the day’s session information into a written summary and sends it through configured webhooks when saved.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ai-report-to-me plugin — 2 commands, 1 hook shipped together

not rated 9repo 6mo ago A scan 0 tokens original MIT

Good fit Use it to generate and save a daily coding report for delivery to connected services.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/fakehank/ai-report-to-me/dayreport
View source ↗ FakeHank/ai-report-to-me
Install

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.

Clone the repo
git clone --depth 1 https://github.com/FakeHank/ai-report-to-me

Made for: Claude Code.

Or install ai-report-to-me, the plugin that ships this one along with the rest of its 2 commands, 1 hook.

Wrote 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.

agentmods badge for dayreport

README.md
[![agentmods](https://agentmods.dev/badge/commands/fakehank/ai-report-to-me/dayreport/github.svg)](https://agentmods.dev/commands/fakehank/ai-report-to-me/dayreport)
Your own site
<a href="https://agentmods.dev/commands/fakehank/ai-report-to-me/dayreport"><img src="https://agentmods.dev/badge/commands/fakehank/ai-report-to-me/dayreport/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for dayreport

Your own site · 80×15
<a href="https://agentmods.dev/commands/fakehank/ai-report-to-me/dayreport"><img src="https://agentmods.dev/badge/commands/fakehank/ai-report-to-me/dayreport.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 505 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00505
Opus 5 $0.00000 $0.00253
Sonnet 5 $0.00000 $0.00101
Haiku 4.5 $0.00000 $0.00051

Measured 12d ago against content hash 241aef3ef9f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

dayreport 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 12d 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.

commands/dayreport.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate a daily report from my coding session data.

Non-negotiable delivery rule

  • A /dayreport run is only considered complete after aireport save-daily --date {SAVE_DATE} --content - succeeds.
  • save-daily is the webhook trigger point. If you skip it, Slack/Feishu/other webhook messages will NOT be sent.
  • Never write ~/.ai-report/reports/{SAVE_DATE}.md directly.

Steps

  1. Run the following command to get the aggregated data and prompt:
aireport daily --prompt-only

  1. Read the output carefully. It contains:

    • A system prompt with instructions on how to generate the report
    • Aggregated session data in JSON format
    • At the end, metadata lines starting with SAVE_DATE= and SESSION_IDS=

  2. Follow the system prompt instructions to generate a complete daily report in Markdown.

  3. After generating the report, save it by piping the content through save-daily:

    • Extract the SAVE_DATE value (e.g. 2026-02-28)
    • Write the generated Markdown to a temp file, then run:
aireport save-daily --date {SAVE_DATE} --content -

Pass the full report markdown via stdin (pipe or heredoc). This command saves the report and pushes to any configured webhooks (Slack, Discord, Feishu, etc.).

MANDATORY: /dayreport must call save-daily. Do NOT write directly to ~/.ai-report/reports/.

  1. Verify send status from command output:

    • Success signal includes lines like [feishu] Report pushed successfully / [slack] Report pushed successfully
    • If webhook push fails, report the failure clearly and keep the run marked as failed-to-deliver

  2. If there are multiple days to generate (the command may output multiple prompts), process them in order. For each subsequent day, include the previous day's key decisions as context.

  3. After saving, tell me the file path and a brief summary of what the report covers.

Notes

  • If the command says "All reports are up to date", just tell me that — no report needed.
  • If the command says "No sessions found", tell me there's no data to report on.
  • The report language follows the output_lang setting in ~/.ai-report/config.json.

Read the full file on GitHub · 49 lines

Changes

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.

  1. 12d ago First seen · 49 lines · 0 tokens per session scan A 241aef3ef9f2

Subscribe to this mod's changes

dayreport is a command published in the GitHub repository FakeHank/ai-report-to-me (9 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 505 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.

Analytics and metricsClaude Codeai-codingclicodexdaily-reportopencode
Related

Other commands, from other repositories

atomic-plan

Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.

damusix/atomic-claude · 54 tokens

follow-up

Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…

damusix/atomic-claude · 0 tokens

review-branch

Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.

damusix/atomic-claude · 35 tokens

session-report

Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.

damusix/atomic-claude · 31 tokens

commit

Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.

damusix/atomic-claude · 55 tokens

create-pr

Create a pull request with proper template discovery and population.

axiomantic/spellbook · 10 tokens