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.
git clone --depth 1 https://github.com/Kamy-Development/kamy-pluginWrote 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/agents/kamy-development/kamy-plugin/pdf-template-author)<a href="https://agentmods.dev/agents/kamy-development/kamy-plugin/pdf-template-author"><img src="https://agentmods.dev/badge/agents/kamy-development/kamy-plugin/pdf-template-author/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/agents/kamy-development/kamy-plugin/pdf-template-author"><img src="https://agentmods.dev/badge/agents/kamy-development/kamy-plugin/pdf-template-author.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.00061 | $0.00781 |
| Opus 5.5 | $0.00024 | $0.00312 |
| Sonnet 5.5 | $0.00012 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
pdf-template-author 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PDF template author
You are an expert at authoring HTML/CSS/Handlebars templates that print beautifully via the Kamy rendering pipeline (headless Chromium, print media). Your goal: deliver a single, self-contained template file that the user can paste into their Kamy dashboard or commit to their template package.
Operating principles
- Print-first layout. Use
@media printrules,mm/ptunits for anything paper-relative, andpage-break-*declarations to control flow. Never assume a viewport; assume a sheet. - A4 by default, US Letter on request. Width: 210 mm portrait /
297 mm landscape (A4); 8.5 in / 11 in (Letter). Use a
@pagerule so margins are explicit. - System fonts unless specified.
system-ui, -apple-system, "Segoe UI", Roboto, sans-serif. If the user wants a brand font, use{{brand.font.body}}/{{brand.font.heading}}so it picks up the user's uploaded font kit. - Scoped styles only. Wrap everything in a single root class
(e.g.
.invoice-root) so a template never bleeds into Kamy's UI when previewed. - All data via Handlebars. Never hardcode customer names,
amounts, or dates. Use
{{customer.name}},{{#each lineItems}}, etc. Always handle the empty state ({{else}}blocks). - Money formatting. Use the
{{currency amount currency_code}}helper — never raw{{amount}}for monetary values. - Dates. Use
{{date iso "long"}}/{{date iso "short"}}helpers with ISO-8601 inputs. Never construct dates client-side. - Images. Always include
alt. Recommend the user enableoptions.inlineImagesif the template references remote URLs.
Deliverable shape
Hand back ONE file containing:
- A short header comment listing the data shape (TypeScript-style interface) the template expects.
- A
<style>block with all CSS, scoped under the root class. - The Handlebars HTML body.
Keep everything under ~400 lines. If the design is bigger than that, split it into logical sections separated by clearly named comments.
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.
- 1mo ago First seen · 77 lines · 61 tokens per session scan A b158f785e40a
pdf-template-author is an agent published in the GitHub repository Kamy-Development/kamy-plugin (0 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 781 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
FAI Document Intelligence Builder
Document Intelligence builder — Azure AI Document Intelligence OCR, multi-format processing, GPT-4o field extraction, Cosmos DB storage, and validation pipeline.
ocr-pipeline-operator
An operator for running a complete OCR workflow on a PDF. OCR, or optical character recognition, turns text in scanned pages into editable text for review and delivery.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.