A command for creating a multi-page report or document layout intended for printing or PDF output. It defines page sizes, margins, repeated page templates, typography, and print-specific CSS rules.

Use it for annual reports, project reports, proposals, invoices, and other structured documents with controlled page geometry.

It removes the need to assemble print layout settings from scratch and helps keep pages consistent when printed or saved as a PDF.

pdf-report — Command for Claude Code by Adityaraj0421/naksha-studio

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.

Clone the repo

git clone --depth 1 https://github.com/Adityaraj0421/naksha-studio

Made for: Claude Code.

Or install naksha, the plugin that ships this one along with the rest of its 1 skill, 70 commands, 7 agents, 9 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/commands/adityaraj0421/naksha-studio/pdf-report/github.svg)](https://agentmods.dev/commands/adityaraj0421/naksha-studio/pdf-report)

Your own site

<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/pdf-report"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/pdf-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/commands/adityaraj0421/naksha-studio/pdf-report"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/pdf-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,532 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.00033	$0.01532
Opus 5.5	$0.00013	$0.00613
Sonnet 5.5	$0.00007	$0.00306
Haiku 4.5	$0.00003	$0.00153

Measured yesterday against content hash afd3ddc7ab09, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pdf-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 yesterday.

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.

commands/pdf-report.md · 146 lines

How it starts

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

/pdf-report $ARGUMENTS

You are activating the Print/PDF Wing in report mode: Print Designer, producing a multi-page print-ready document with CSS @page geometry, named pages, master template, and a full preflight checklist.

Process

1. Parse Input

Extract from $ARGUMENTS:

Subject — what the report covers (e.g., "Q4 performance", "annual review", "project proposal")
Brand name — used for color references and logo placement
Document type — annual report / project report / proposal / invoice / other (default: annual report)
Page count — specific number or "auto" (generate all necessary sections)

Identify:

Primary audience: internal (colleagues) / client-facing / regulatory / public
Color preference: full-color / two-color / black and white (default: full-color)

2. Page Geometry

Set up the @page rules for all named page types:

@page { size: A4; margin: 20mm 20mm 25mm 20mm; }
@page cover { size: A4; margin: 0; }
@page toc   { size: A4; margin: 20mm; }
@page body  {
  size: A4; margin: 20mm 20mm 25mm 20mm;
  @top-right   { content: string(chapter-title); font-size: 9pt; color: #6b7280; }
  @bottom-right { content: "Page " counter(page) " of " counter(pages); font-size: 9pt; }
}
@page back { size: A4; margin: 0; }

Apply page assignments: .cover { page: cover; } / .toc { page: toc; } / .chapter { page: body; break-before: page; } / .back { page: back; }.

3. Master Template Structure

Define HTML structure for all 4 page types:

Cover: full-bleed hero <div> (background extends to artboard edge via negative margin + print-color-adjust: exact), title H1, brand name, report date
TOC: two-column list with leaders (use flex + border-bottom: 1px dotted #9ca3af as CSS workaround for leader(dotted))
Section page: <header> with H1 (sets string-set: chapter-title content()), body column at 60–75 chars per line, pull quote margin area
Back cover: brand lockup centered, contact details, bleed background

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

yesterday First seen · 146 lines · 33 tokens per session scan A afd3ddc7ab09

Subscribe to this mod's changes

pdf-report is a command published in the GitHub repository Adityaraj0421/naksha-studio (343 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 1,532 once invoked, about $0.0001 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-10-19.

Design and UX Documents PDF ai claude-code-plugin design-system figma

print-export-designer

Use when something has to leave the screen. PDF generation, print stylesheets, receipts and invoices, exported reports, or a download that gives the user no feedback.

imsaif/design-with-claude · 33 tokens

brand

Generate a full editorial brand-guidelines book for any URL. 14 chapters covering brand essence/archetype, colour, typography, spacing, shape, iconography, motion, components, voice, accessibility, tokens, and how-to-use guidance. Print-ready, dark-mode toggle, hand-off-ready single HTML.

Manavarya09/design-extract · 62 tokens

pdf-report