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.
/plugin marketplace add robertgorsuch/AI-JasperReports-Generator/plugin install jasper-deployWrote 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.
[](https://agentmods.dev/commands/robertgorsuch/ai-jasperreports-generator/smoke)<a href="https://agentmods.dev/commands/robertgorsuch/ai-jasperreports-generator/smoke"><img src="https://agentmods.dev/badge/commands/robertgorsuch/ai-jasperreports-generator/smoke/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.
<a href="https://agentmods.dev/commands/robertgorsuch/ai-jasperreports-generator/smoke"><img src="https://agentmods.dev/badge/commands/robertgorsuch/ai-jasperreports-generator/smoke.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00019 | $0.00187 |
| Opus 5 | $0.00010 | $0.00093 |
| Sonnet 5 | $0.00004 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
smoke 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.
What it actually says
Read ${CLAUDE_PLUGIN_ROOT}/skills/jasper-deploy/SKILL.md (and LOCAL.md next
to it if present). Ensure $env:PGPASSWORD is set (see SKILL.md Conventions),
then run:
& "${CLAUDE_PLUGIN_ROOT}/skills/jasper-deploy/scripts/smoke_test.ps1"
It runs offline prechecks (doc consistency + Pester unit tests) and then the
full server lifecycle under a throwaway /reports/_smoke folder. Report the
result step by step. On a failure, look the symptom up in
${CLAUDE_PLUGIN_ROOT}/skills/jasper-deploy/references/gotchas.md before
diagnosing from scratch, and quote the matching entry if one exists.
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.
- 9d ago First seen · 18 lines · 19 tokens per session scan A 599e3f583db9
smoke is a command published in the GitHub repository robertgorsuch/AI-JasperReports-Generator (1 stars, last pushed 11d ago), licensed Apache-2.0. It adds 19 tokens to every session and 187 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.
Other commands, from other repositories
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
test-accounts
Show PayPal sandbox test accounts and scenario-specific testing tips.
test
Test commit. Use for add tests, update tests, test coverage, unit test, spec.
engineer
Guided full-project lifecycle - walks intake → plan (sign-off) → autonomous build → quality gates → CI/finish, invoking the right claude-engineer skill at each stage.
test
Generate API integration tests for endpoints.
quality
Command "quality" from iwritec0de/app-dev, covering quality gate, usage, arguments, instructions and /quality run.