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/FakeHank/ai-report-to-meWrote 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/fakehank/ai-report-to-me/qtreport)<a href="https://agentmods.dev/commands/fakehank/ai-report-to-me/qtreport"><img src="https://agentmods.dev/badge/commands/fakehank/ai-report-to-me/qtreport/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.
<a href="https://agentmods.dev/commands/fakehank/ai-report-to-me/qtreport"><img src="https://agentmods.dev/badge/commands/fakehank/ai-report-to-me/qtreport.svg" alt="Reviewed on agentmods" width="80" 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.00655 |
| Opus 5 | $0.00000 | $0.00328 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
qtreport 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 11d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a 90-day Vibe Coding Wrapped report from my coding session data.
Steps
- Run the following command to get the aggregated data and prompt:
aireport wrapped --days 90 --prompt-only
-
Read the output carefully. It contains:
- A system prompt with detailed instructions for generating the 8-section Wrapped report
- Aggregated session data including: session stats, project breakdown, vibe signals, habit analysis, improvement suggestions
- At the end, metadata lines starting with
SAVE_PERIOD=andSESSION_IDS=
-
Follow the system prompt instructions to generate the complete Wrapped report with all 8 sections.
-
After generating the report, save it by piping the content through
save-wrapped:- Extract the
SAVE_PERIODvalue (e.g.2026-01-01_2026-03-31),SESSION_IDS, andSTATS - Run:
- Extract the
aireport save-wrapped --period {SAVE_PERIOD} --session-ids {SESSION_IDS} --stats {STATS} --content -
Pass the full report markdown via stdin (pipe or heredoc). The --stats flag passes pre-computed stats so the card generator doesn't need to re-read all sessions. This command saves the report, generates the vibe card PNG, and pushes to any configured webhooks.
Do NOT write directly to ~/.ai-report/wrapped/ — always use save-wrapped so webhooks are triggered.
- After saving, do the following:
- Tell me the exact file paths for both the Wrapped markdown report and the vibe card PNG (e.g.
~/.ai-report/wrapped/2026-01-01_2026-03-31.mdand~/.ai-report/wrapped/vibe-card-2026-01-01_2026-03-31.png) - Highlight the Vibe Coder type result and the roast quote
- Immediately open the vibe card PNG so I can see it (do NOT ask, just open it):
- Tell me the exact file paths for both the Wrapped markdown report and the vibe card PNG (e.g.
open ~/.ai-report/wrapped/vibe-card-{PERIOD}.png
(On Linux, use xdg-open instead of open.)
-
Then naturally ask if I'd like to share the vibe card to X (Twitter). Keep the tone conversational — don't use numbered lists or formal option menus. Just ask casually, like a friend would.
-
If I agree, open the X compose page:
open "https://x.com/intent/post?text=My%20Vibe%20Coder%20type%20from%20%40AiReportToMe"
2. Tell me to drag the PNG from the preview window into the X compose window.
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.
- 11d ago First seen · 56 lines · 0 tokens per session scan A 4c00153691b2
qtreport 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 655 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
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.
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…
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.
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.
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.
feature-discover
Phase 1.5 of develop: Informed discovery, disambiguation, 7-category questions, understanding document, devil's advocate.