A report of one orchestrated run's timeline, including time spent in each state, rejections, hook decisions, and cost.

Use it to inspect a run's current state, dwell times, denials, bypasses, rejection count, and token spending.

It combines existing run records so you can understand what happened during a session without reading the full transcript.

run-report — Skill for Claude Code by bdfinst/agentic-dev-team

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add bdfinst/agentic-dev-team

Claude Code

/plugin install dev-team

Made for: Claude Code.

Or install dev-team, the plugin that ships this one along with the rest of its 98 skills, 54 agents, 4 hooks.

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/bdfinst/agentic-dev-team/run-report/github.svg)](https://agentmods.dev/skills/bdfinst/agentic-dev-team/run-report)

Your own site

<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/run-report"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/run-report/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/run-report"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/run-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 783 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.

Model	Per session	Once invoked
Fable 5.1	$0.00115	$0.00783
Opus 5.5	$0.00046	$0.00313
Sonnet 5.5	$0.00023	$0.00157
Haiku 4.5	$0.00012	$0.00078

Measured 1mo ago against content hash 6f5c4c798fee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

run-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 1mo 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.

plugins/dev-team/skills/run-report/SKILL.md · 71 lines

How it starts

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

Run Report (#1167)

Role: worker. Reports one session_id's composed run timeline by joining the existing deterministic metrics streams — no model tokens spent parsing transcripts.

workflow-states.jsonl (#1166) records only state transitions; current state and per-state dwell time are always derived by replay (hooks/lib/workflow_state.py::derive_current_state() / compute_dwell_times()). boundary-events.jsonl records every guard hook's block/warn/bypass decision. cost-metering.jsonl records per-session token spend, but is keyed by transcript filename, not session_id — see Join limitations below.

Steps

Run the report. If the user passes --session <id>, use it; otherwise let the library auto-detect the most recent session_id seen across boundary-events.jsonl and workflow-states.jsonl:
```
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/lib/run_report.py" report --session <id>
```
Present a readable summary, not raw JSON. Render the JSON the library prints as a short table/summary:
- session_id and current_state
- a dwell_seconds table, one row per state
- rejection_count and bypass_count
- denials_by_cause as a table of matched_rule -> count
- the cost section: if joinable is false, say so plainly and show reason plus the most_recent_entry (if any) labeled as a rough, unattributed proxy — never present it as this session's actual cost.
If a stream file is absent, its section is simply empty (zero counts, no dwell times) — that is not an error; say so rather than treating it as a failure.

Join limitations

cost-metering.jsonl entries are written by the Stop hook (hooks/cost_meter.py → hooks/lib/cost_meter.py::cmd_record()) keyed by transcript filename — the hook never learns the session ID, so there is no reliable per-session join key today. Rather than guess an attribution the data doesn't support, the report marks cost.joinable: false and surfaces only the most recent recorded entry as an unattributed reference point. A future stream-schema change adding session_id to cost-metering.jsonl would let this become a real join.

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

1mo ago First seen · 71 lines · 115 tokens per session scan A 6f5c4c798fee

Subscribe to this mod's changes

run-report is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 115 tokens to every session and 783 once invoked, about $0.0005 per session on Opus 5.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-09-03.

Analytics and metrics

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

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

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

obra/superpowers · 21 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

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.