octoperf-export-bench-report-pdf

octoperf-export-bench-report-pdf is a skill for Claude Code from OctoPerf/octoperf-claude-plugins. It costs 96 tokens per session (1,094 once invoked), scanned A, original, Apache-2.0.

A tool for turning an OctoPerf bench report into a PDF file. OctoPerf is a service for testing system performance under load, and a bench report contains results from such a test.

In plain words
What is it for?
Use it to export an existing report after its test and data updates have finished. The export process submits the print job, waits for it to complete, and downloads the PDF.
Why use it?
It creates a fixed document that can be shared, attached to a ticket, or stored offline. It is intended for handing off results rather than querying individual metrics.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the octoperf plugin — 20 skills, 1 MCP server shipped together

Good fit Use it to export an existing report after its test and data updates have finished. The export process submits the print job, waits for it to complete, and downloads the PDF.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/octoperf/octoperf-claude-plugins/octoperf-export-bench-report-pdf
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 OctoPerf/octoperf-claude-plugins --skill octoperf-export-bench-report-pdf
Clone the repo
git clone --depth 1 https://github.com/OctoPerf/octoperf-claude-plugins

Made for: Claude Code.

Or install octoperf, the plugin that ships this one along with the rest of its 20 skills, 1 MCP server.

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 octoperf-export-bench-report-pdf

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/octoperf/octoperf-claude-plugins/octoperf-export-bench-report-pdf"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-export-bench-report-pdf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,094 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.00096 $0.01094
Opus 5 $0.00048 $0.00547
Sonnet 5 $0.00019 $0.00219
Haiku 4.5 $0.00010 $0.00109

Measured 12d ago against content hash 3d5cfae2b9e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

octoperf-export-bench-report-pdf 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/octoperf/skills/octoperf-export-bench-report-pdf/SKILL.md · 105 lines

How it starts

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

OctoPerf — Export a benchReport as PDF

OctoPerf prints reports server-side with a headless Playwright render. The work is async: the MCP tool submits the task, the LLM polls until it settles, then pulls the PDF off the report's first bench result.

When this applies

The user wants a static, shareable artefact of an existing bench report — a stakeholder review, an attachment to a ticket, an offline archive. If the user just wants to read metrics, use the report value tools (get_report_summary_values, get_report_table_values, …) instead. The PDF is for hand-off, not analysis.

Prerequisites

  • A benchReportId (find it with list_bench_reports_by_project).
  • The underlying bench run is terminal (FINISHED / ABORTED / ERROR). Printing a report whose run is still RUNNING is allowed but the metrics inside the PDF will be partial.
  • The report's data is up to date. export_bench_report_pdf refuses otherwise, rather than rendering a document of empty report items: run get_report_data_status, then update_report_data, and print once the update tasks reach SUCCESS. See octoperf-bench-reports.

The three-step chain

1. Submit the print task

export_bench_report_pdf(benchReportId)
# returns { benchReportId, taskId }

The tool returns immediately with a taskId. Defaults are sensible (portrait A4, empty cover page, en-US locale, UTC timezone) — no extra parameters needed for the common case.

2. Poll until the task settles

get_task_result(taskId)
# returns { taskId, status, message }

status cycles through PENDING while Playwright is rendering. Stop on:

  • SUCCESS → the PDF has been uploaded to the report's first bench result. Continue with step 3.
  • FAILEDmessage carries the backend stack trace. Surface it to the user verbatim and stop.

Typical render time is 10–30 seconds; expect more on large reports (many report items, long trend series). For the polling cadence and the sleep-between-polls discipline, read octoperf-async-polling — the PDF task is in its table (3s between polls, ~5 min outer deadline).

Read the full file on GitHub · 105 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 First seen · 105 lines · 96 tokens per session scan A 3d5cfae2b9e4

Subscribe to this mod's changes

octoperf-export-bench-report-pdf is a skill published in the GitHub repository OctoPerf/octoperf-claude-plugins (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 96 tokens to every session and 1,094 once invoked, about $0.0005 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-31.