A command that creates human-readable reports from Akari data, including operational status, research findings, project health, or experiment comparisons.

Use it to report system health, research results, project status, or differences between experiments, with optional date, project, or experiment filters.

It turns session, project, and experiment information into a structured summary for review.

report — Skill for Claude Code and Codex by victoriacity: A command that creates human-readable reports from Akari data…

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.

agentmods

npx agentmods add skills/victoriacity/openakari/report

Any agent

npx skills add victoriacity/openakari --skill report

Clone the repo

git clone --depth 1 https://github.com/victoriacity/openakari

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/victoriacity/openakari/report.svg)](https://agentmods.dev/skills/victoriacity/openakari/report)

Your own site

<a href="https://agentmods.dev/skills/victoriacity/openakari/report"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/report.svg" alt="Measured on agentmods" height="20"></a>

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 684 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00019	$0.00684
Opus 5	$0.00010	$0.00342
Sonnet 5	$0.00004	$0.00137
Haiku 4.5	$0.00002	$0.00068

Measured 5d ago against content hash b651bfad5a12, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 5d 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.

.claude/skills/report/SKILL.md · 67 lines

How it starts

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

/report [options]

Generate a formatted report with charts from akari's data sources.

Report types

Type	Argument	What it shows
Operational	`operational`	Session health, cost trend, budget burn rates, verification compliance
Research digest	`research`	Experiments completed, findings, decision records, knowledge output
Project status	`project [project=<name>]`	Per-project health, tasks, budget, experiments, log entries
Experiment comparison	`experiment-comparison [ids=<id1,id2>]`	Side-by-side experiment results and parameter diffs

Procedure

Step 1: Parse arguments

Extract from the user's message:

type: one of operational, research, project, experiment-comparison (default: operational)
project: optional project name filter (for project and experiment-comparison types)
from: optional start date (ISO format, default: 7 days ago)
to: optional end date (ISO format, default: today)
ids: optional comma-separated experiment IDs (for experiment-comparison)

Step 2: Generate report

Run the report generator:

cd infra/scheduler && npx tsx src/report/run-report.ts --type <type> [--project <name>] [--from YYYY-MM-DD] [--to YYYY-MM-DD] [--ids id1,id2]

This generates:

A markdown report at reports/<type>-<date>.md
Chart images at reports/charts/*.png

Step 3: Display results

Read the generated markdown report file.
Present the key findings to the user, including:
- Summary statistics
- Notable trends or warnings
- Budget alerts (if any resources >80% consumed)
Mention the chart files generated in reports/charts/.

Step 4: Commit (if requested)

If the user wants to preserve the report:

git add reports/
git commit -m "report: <type> <date>"

Examples

/report operational — generates operational dashboard for the last 7 days
/report research from=2026-02-10 — research digest since Feb 10
/report project project=sample-project — sample-project status
/report experiment-comparison ids=strategic-100,model-comparison-focused-v2 — compare two experiments

Read the full file on GitHub · 67 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.

5d ago First seen · 67 lines · 19 tokens per session scan A b651bfad5a12

Subscribe to this mod's changes

report is a skill published in the GitHub repository victoriacity/openakari (47 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 684 once invoked, about $0.0001 per session on Opus 5. 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.

Research Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens