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 skills/ronmkr/promptbook/session-reportnpx skills add ronmkr/PromptBook --skill session-reportgit clone --depth 1 https://github.com/ronmkr/PromptBookWrote 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/skills/ronmkr/promptbook/session-report)<a href="https://agentmods.dev/skills/ronmkr/promptbook/session-report"><img src="https://agentmods.dev/badge/skills/ronmkr/promptbook/session-report.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.00035 | $0.00801 |
| Opus 5 | $0.00017 | $0.00400 |
| Sonnet 5 | $0.00007 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
session-report 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.
This is a copy
92% identical to session-report — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Report
Produce a self-contained HTML report of Antigravity usage and save it to the current working directory.
Steps
-
Get data. Run the bundled analyzer (default window: last 7 days; honor a different range if the user passed one, e.g.
24h,30d, orall). The scriptanalyze-sessions.mjslives in the same directory as this SKILL.md — use its absolute path:node <skill-dir>/analyze-sessions.mjs --json --since 7d > /tmp/session-report.jsonFor all-time, omit
--since. -
Read
/tmp/session-report.json. Skimoverall,by_project,by_subagent_type,by_skill,cache_breaks,top_prompts. -
Copy the template (also bundled alongside this SKILL.md) to the output path in the current working directory:
cp <skill-dir>/template.html ./session-report-$(date +%Y%m%d-%H%M).html -
Edit the output file (use Edit, not Write — preserve the template's JS/CSS):
- Replace the contents of
<script id="report-data" type="application/json">with the full JSON from step 1. The page's JS renders the hero total, all tables, bars, and drill-downs from this blob automatically. - Fill the
<!-- AGENT: anomalies -->block with 3–5 one-line findings. Express figures as a % of total tokens wherever possible (total =overall.input_tokens.total + overall.output_tokens). One line per finding, exact markup:
Classes:<div class="take bad"><div class="fig">41.2%</div><div class="txt"><b>cc-monitor</b> consumed 41% of the week across just 3 sessions</div></div>.take badfor waste/anomalies (red),.take goodfor healthy signals (green),.take infofor neutral facts (blue). The.figis one short number (a %, a count, or a multiplier like12×). The.txtis one plain-English sentence naming the project/skill/prompt; wrap the subject in<b>. Look for: a project or skill eating a disproportionate share, cache-hit <85%, a single prompt >2% of total, subagent types averaging >1M tokens/call, cache breaks clustering. - Fill the
<!-- AGENT: optimizations -->block (at the bottom of the page) with 1–4<div class="callout">suggestions tied to specific rows (e.g. "/weekly-statusspawned 7 subagents for 8.1% of total — scope it to fewer parallel agents"). - Do not restructure existing sections.
- Replace the contents of
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 43 lines · 35 tokens per session scan A 142dfe2d339b
session-report is a skill published in the GitHub repository ronmkr/PromptBook (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 801 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to session-report, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
bug-audit
Weekly multi-agent audit for serious bugs (data integrity, silent caps, staleness, timestamp math, trust boundaries). Fans out Sonnet scanners + Opus deep auditors, adversarially verifies every finding, files GitHub issues for confirmed critical/high bugs. Trigger: /bug-audit.
multi-llm-review
Run complete, evidence-backed code reviews through the local stdio gateway across the seven canonical CLI providers: Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. Use for quality, security, correctness, or release validation that requires independent reviewers.
retrospective-walk
Walk a human or agent through a diff, worktree, commit range, gateway job, or episode reference as a structured retrospective. Use after implement-review-fix or multi-LLM review cycles, when reviewing prior jobs or uncommitted work, or when durable evidence is needed for what changed, why it changed, who/when…
secure-orchestration
Orchestrate security-sensitive LLM work with the gateway's Claude-managed approval boundary, provider-native legacy controls, evidence-aware auditing, and complete no-limit review handling.
session-workflow
Manage gateway bookkeeping and provider-native conversation continuity across Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. Use for multi-turn work, session inspection, and safe resume decisions.