report

report is a command for Claude Code from jamditis/claude-skills-journalism. It costs 11 tokens per session (555 once invoked), scanned A, original, MIT.

A command for creating a print-ready HTML program or annual report with an organisation’s branding, structured sections and data displays.

In plain words
What is it for?
Use it for cover pages, summaries, highlights, detailed sections, tables, charts, quotes and publication dates.
Why use it?
It avoids formatting the report from scratch and applies saved colours, fonts and naming throughout the document.

Command 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 pdf-playground plugin — 1 skill, 8 commands shipped together

Good fit Use it for cover pages, summaries, highlights, detailed sections, tables, charts, quotes and publication dates.

Compare 6 commands from other repositories ↓
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 jamditis/claude-skills-journalism
Claude Code
/plugin install pdf-playground

Made for: Claude Code.

Or install pdf-playground, the plugin that ships this one along with the rest of its 1 skill, 8 commands.

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/commands/jamditis/claude-skills-journalism/report/github.svg)](https://agentmods.dev/commands/jamditis/claude-skills-journalism/report)
Your own site
<a href="https://agentmods.dev/commands/jamditis/claude-skills-journalism/report"><img src="https://agentmods.dev/badge/commands/jamditis/claude-skills-journalism/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/commands/jamditis/claude-skills-journalism/report"><img src="https://agentmods.dev/badge/commands/jamditis/claude-skills-journalism/report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 555 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.00011 $0.00555
Opus 5 $0.00005 $0.00278
Sonnet 5 $0.00002 $0.00111
Haiku 4.5 $0.00001 $0.00056

Measured 9d ago against content hash efbe61906283, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 9d 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.

pdf-playground/commands/report.md · 74 lines

How it starts

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

Create a print-ready HTML program report document.

Version check

Read the plugin version from ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json and note it. If the file doesn't exist or the read fails, warn the user that the plugin may not be properly installed.

Setup

  1. Check for brand configuration at .claude/pdf-playground.local.md
  2. If found, parse the YAML frontmatter for brand settings
  3. If not found, ask the user for their organization name and primary brand color
  4. Load the report template from ${CLAUDE_PLUGIN_ROOT}/templates/report-template.html
  5. Read the document-design skill for CSS patterns

Brand application

Apply brand settings to the template:

  • Replace organization name throughout
  • Update CSS variables with brand colors
  • Set font families from brand config
  • Apply heading case style

Document structure

Page 1 - Cover page:

  • Organization branding
  • Report title in configured case
  • Subtitle (e.g., "Annual report 2025")
  • Date range or publication date

Page 2+ - Content sections:

  • Executive summary
  • Key metrics or highlights (use callout boxes)
  • Detailed sections with headings
  • Data visualizations or tables
  • Quotes and testimonials

Final page:

  • Contact information
  • Acknowledgments
  • Organization info

Report name

The report name is: $ARGUMENTS

If no report name provided, ask the user for:

  • Report title
  • Time period covered
  • Key sections to include
  • Any metrics or data to highlight

Content MUST NOT touch or overlap the page footer.

  • The .page element MUST use display: grid; grid-template-rows: auto 1fr auto
  • It MUST have exactly 3 direct children: <header class="page-header">, <div class="page-body">, <footer class="page-footer">
  • The content wrapper (.page-body) MUST have overflow: hidden to prevent text bleeding
  • Never use position: absolute for footers, keep them in normal document flow as the third grid row
  • After generating, always take a screenshot and visually verify the bottom of each page
  • If content is too long, reduce content rather than shrinking the footer gap

Read the full file on GitHub · 74 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. 9d ago First seen · 74 lines · 11 tokens per session scan A efbe61906283

Subscribe to this mod's changes

report is a command published in the GitHub repository jamditis/claude-skills-journalism (389 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 555 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.