deploy

deploy is a command for Claude Code from robertgorsuch/AI-JasperReports-Generator. It costs 16 tokens per session (254 once invoked), scanned A, original, Apache-2.0.

A command workflow for creating, compiling, deploying, and checking a JasperReports report. JasperReports is a reporting system that produces formatted documents such as PDFs from report definitions and data queries.

In plain words
What is it for?
Use it with an existing JRXML report file, an SQL query, or a written report description. It scaffolds when needed, runs the compile and deployment checks, and verifies the result by rendering it.
Why use it?
It provides a defined path from a report description or SQL query to a deployed report and checks whether the server can render it. It also directs common fill-time errors to the relevant troubleshooting notes.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the jasper-deploy plugin — 1 skill, 4 commands shipped together

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.

agentmods
npx agentmods add commands/robertgorsuch/ai-jasperreports-generator/deploy
Clone the repo
git clone --depth 1 https://github.com/robertgorsuch/AI-JasperReports-Generator

Made for: Claude Code.

Or install jasper-deploy, the plugin that ships this one along with the rest of its 1 skill, 4 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 deploy

README.md
[![agentmods](https://agentmods.dev/badge/commands/robertgorsuch/ai-jasperreports-generator/deploy.svg)](https://agentmods.dev/commands/robertgorsuch/ai-jasperreports-generator/deploy)
Your own site
<a href="https://agentmods.dev/commands/robertgorsuch/ai-jasperreports-generator/deploy"><img src="https://agentmods.dev/badge/commands/robertgorsuch/ai-jasperreports-generator/deploy.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 254 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00016 $0.00254
Opus 5 $0.00008 $0.00127
Sonnet 5 $0.00003 $0.00051
Haiku 4.5 $0.00002 $0.00025

Measured 5d ago against content hash 16f579c24dc7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

deploy 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 5d 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/jasper-deploy/commands/deploy.md · 22 lines

What it actually says

Read ${CLAUDE_PLUGIN_ROOT}/skills/jasper-deploy/SKILL.md (and LOCAL.md next to it if present) and follow its "core happy path".

Arguments given: $ARGUMENTS

  • If the argument is an existing .jrxml file, skip scaffolding and start at the compile step.
  • If it is a SQL query (or the user described the report in words), scaffold first with scaffold_jrxml.py (flags in references/reports.md).
  • Deploy with deploy_report.ps1 (the lint gate runs automatically — do not skip it), then verify with verify_report.ps1 / run-to-PDF and report the HTTP status and output location.
  • No target URI given → ask where in the repository the report should live before deploying.
  • On any 400 at fill time, check references/gotchas.md first (strict-Jackson and leading-WITH SQL are the usual culprits).
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. 5d ago First seen · 22 lines · 0 tokens per session scan A 16f579c24dc7

Subscribe to this mod's changes

deploy is a command published in the GitHub repository robertgorsuch/AI-JasperReports-Generator (1 stars, last pushed 8d ago), licensed Apache-2.0. It adds 16 tokens to every session and 254 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-31.