agentmods.dev

report

report is a skill for Claude Code from emaballarin/ccplugins. It costs 109 tokens per session (802 once invoked), scanned A, original, MIT.

A report-writing skill for completed autoresearch runs, using the recorded experiments and Git history to create a final Markdown summary.

In plain words
What is it for?
Use it after an optimisation run to document the baseline, best result, improvement path, noise-floor confidence and next experiments.
Why use it?
It turns a machine-readable experiment log into an account of the goal, results, successful changes, failed attempts and remaining uncertainty.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ar plugin — 5 skills shipped together

not rated 4repo changed 12d ago A scan 109 tokens original MIT

Good fit Use it after an optimisation run to document the baseline, best result, improvement path, noise-floor confidence and next experiments.

Compare 6 skills from other repositories ↓
View source ↗ emaballarin/ccplugins
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 emaballarin/ccplugins
Claude Code
/plugin install ar

Made for: Claude Code.

Or install ar, the plugin that ships this one along with the rest of its 5 skills.

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.

agentmods badge for report

README.md
[![agentmods](https://agentmods.dev/badge/skills/emaballarin/ccplugins/report/github.svg)](https://agentmods.dev/skills/emaballarin/ccplugins/report)
Your own site
<a href="https://agentmods.dev/skills/emaballarin/ccplugins/report"><img src="https://agentmods.dev/badge/skills/emaballarin/ccplugins/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.

agentmods 80×15 button for report

Your own site · 80×15
<a href="https://agentmods.dev/skills/emaballarin/ccplugins/report"><img src="https://agentmods.dev/badge/skills/emaballarin/ccplugins/report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 802 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00109 $0.00802
Opus 5.5 $0.00044 $0.00321
Sonnet 5.5 $0.00022 $0.00160
Haiku 4.5 $0.00011 $0.00080

Measured 12d ago against content hash 03122e430202, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 12d 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/autoresearch/skills/report/SKILL.md · 61 lines

How it starts

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

/ar:report — write the run up

Turn the record into something a person can read. Do not iterate.

Steps

  1. Read state (cat ./.ar/ar.jsonl, plus worklog.md and results.tsv if present). No ar.jsonl means nothing to report — say so and stop.

  2. Reconstruct the run per ${CLAUDE_PLUGIN_ROOT}/references/resume-loop.md §1, across all segments, not just the last: a segment boundary marks a harness or baseline change, so metrics either side of it are not comparable and the report must say where the boundaries fell rather than plotting through them.

  3. Pull the winner chain from git — it is an independent record of the same run:

    git log --format='%h %s' --grep='"status":"keep"' <config.branch>
git diff <config.snapshotCommit>..<bestCommit> --stat

  4. Write ./.ar/final_report.md:

    • Goal and setup — objective, metric, direction, harness, budget.
    • Result — baseline → best, absolute and relative, with the confidence tier. State plainly whether the total gain clears the noise floor; a run that ended inside its own scatter did not find anything, and the report says so rather than dressing it up.
    • Trajectory — the keep chain, each with commit, metric, delta and the one-line description of the change.
    • What worked — the winning changes and, where the record supports it, why they worked. Distinguish an explanation from a guess.
    • What failed — discarded families of hypotheses. This is the part with the most reuse value; a future run should not re-derive these.
    • Caveats — crashes, checks_failed iterations, seeds that disagreed, segment boundaries.
    • Next — the strongest untried ideas, from ideas.md and the plateau history.

  5. Report the path. .gitignore carries !.ar/final_report.md, so the report is trackable if it should be committed — offer, do not commit unasked.

Hard rules

  1. Write final_report.md and nothing else. No iterating, no commits, no branch switches, no reverts.
  2. Every number comes from ar.jsonl or git. Never recompute or estimate one.
  3. Report failures and null results as prominently as wins. A loop that banked noise is a finding; concealing it wastes the next run.

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

  1. 12d ago Changed 03122e430202
  2. 1mo ago First seen · 61 lines · 109 tokens per session scan A ceca4dca7bc5

Subscribe to this mod's changes

report is a skill published in the GitHub repository emaballarin/ccplugins (4 stars, last pushed 7d ago), licensed MIT. It adds 109 tokens to every session and 802 once invoked, about $0.0004 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-08-31.

Claude CodeWriting and docsclaude-code-pluginclaude-skills
Related

Other skills, from other repositories

sxo

Search Experience Optimization (SXO), the bridge between SEO and UX/CRO. Audits the journey from the SERP click to the on-page goal: click-through factors (title, meta, rich results), then post-click signals that keep users and drive conversions: above-the-fold relevance and intent match, page speed / Core Web Vitals…

nowork-studio/notfair-plugin · 211 tokens

meta-tags-optimizer

Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…

nowork-studio/notfair-plugin · 91 tokens

critical-code-reviewer

Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.

posit-dev/skills · 67 tokens

shiny-bslib

Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…

posit-dev/skills · 107 tokens

elixir-idioms

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

oliver-kriska/claude-elixir-phoenix · 44 tokens

tidewave-integration

Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.

oliver-kriska/claude-elixir-phoenix · 38 tokens