What is agent-report?

A file-based transport for reports from agents dispatched to do work. It makes the coordinating command collect complete report files rather than relying on possibly missing or shortened final messages.

Use it when coordinating review, research, planning, opinion, backlog, or team agents and collecting their written results.

It prevents an empty or truncated agent response from being mistaken for a report with no findings. It also provides a required location for each dispatched agent's report.

agent-report — Skill for Claude Code by restarter/lets-workflow

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.

Any agent

npx skills add restarter/lets-workflow --skill agent-report

Clone the repo

git clone --depth 1 https://github.com/restarter/lets-workflow

Made for: Claude Code.

Or install lets, the plugin that ships this one along with the rest of its 20 skills, 26 commands, 16 agents.

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/restarter/lets-workflow/agent-report/github.svg)](https://agentmods.dev/skills/restarter/lets-workflow/agent-report)

Your own site

<a href="https://agentmods.dev/skills/restarter/lets-workflow/agent-report"><img src="https://agentmods.dev/badge/skills/restarter/lets-workflow/agent-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/restarter/lets-workflow/agent-report"><img src="https://agentmods.dev/badge/skills/restarter/lets-workflow/agent-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,775 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.00054	$0.02775
Opus 5.5	$0.00022	$0.01110
Sonnet 5.5	$0.00011	$0.00555
Haiku 4.5	$0.00005	$0.00278

Measured 2d ago against content hash 7ab84ed78f97, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/lets/skills/agent-report/SKILL.md · 111 lines

How it starts

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

Agent Report

A Task agent's final text is a lossy channel: it arrives empty or cut near 4 KB, and an empty result reads exactly like "no findings" (lets-1irms). Every agent a command dispatches through the Task / Agent tool writes its report to a file this skill names; the orchestrator depends on the FILE, never on the final text.

Files are INPUT, never the deliverable. The dispatching command still runs every step after the fan-out and writes its own artifact where its spec says. Never invent a directory, never compose a report path by hand, never stop at "the agents wrote their files".

op=open - before the first dispatch of a run

Skill(skill: "lets:artifact-path", args: "kind=reports-{command} ext=dir task={task-id}") -> REPORT_DIR = the echoed ARTIFACT_FILE (a directory, already created). No echo -> STOP: dispatch nothing, surface the error.
One file per dispatched agent: {REPORT_DIR}/{name}.md. name is the caller's - the agent short name (security), suffixed when one agent type runs several times in the run (skeptic-f3-2, architect-b). [a-z0-9.-] only (a beads id may carry .N), unique within the run. A name never starts with report, summary, findings or analysis (any case): Claude Code's Write tool refuses a subagent's .md whose basename starts with one of them, and the report is lost (lets-jyjxc). A name never ends in -r<digits>: that suffix is Step 3's retry. reportnames_test.go pins both for every template in the plugin.
Output REPORT_DIR=<dir> and one REPORT_FILE <name>=<path> line per name.

Every dispatch prompt carries its agent's path as its own line, right after the PROJECT_ROOT line (or first, when the prompt has none):

REPORT_FILE: <absolute path>

op=add - a later phase of the same run

Args: dir=<REPORT_DIR> names=<name>,<name>. Same naming as op=open step 2 in the SAME directory - one run keeps one directory (review: reviewers, then skeptics; opinion: panel, then challenge; plan: explorers, architects, experts). No artifact-path call. Run as written:

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

2d ago Changed · +22 lines 7ab84ed78f97
20d ago First seen · 89 lines · 54 tokens per session scan A a169c335e043

Subscribe to this mod's changes

agent-report is a skill published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 2,775 once invoked, about $0.0002 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-27.

Building agents Claude Code Code review ai-agents claude-code-plugin cli developer-tools

dekko-verify

Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…

aahlijia/dekko · 151 tokens

dekko-review-context

Give a code-review or PR-description flow a structural head start before reading a diff line by line. Trigger when the user asks for a PR description, a pre-merge summary, or invokes a code-review flow (/code-review, /review, or an equivalent) against a diff in a repo with a .dekko/ directory.

aahlijia/dekko · 74 tokens

triage-report

Drain the .review/ report queue. Resolves un-triaged scan/audit reports (producer-agnostic — check-docs-consistency and any other scanner), dispatches the triage-report subagent (Sonnet) one report at a time for per-finding dispositions (promote / patch / dup / needs-investigation / dismiss), then the gateway absorbs…

RockyHong/super-bootstrap · 151 tokens

agent-report