Knowledge Work Plugins is an open-source collection of Claude extensions organized around roles such as productivity, sales, and customer support. Each plugin combines role-specific guidance, connectors, commands, and sub-agents so knowledge workers can use Claude with their team’s tools and processes. The catalogue entries are examples of, or workflows from, this plugin collection.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/anthropics/knowledge-work-pluginsnpx agentmods add commands/anthropics/knowledge-work-plugins/fill-formWrote 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/anthropics/knowledge-work-plugins/fill-form)<a href="https://agentmods.dev/commands/anthropics/knowledge-work-plugins/fill-form"><img src="https://agentmods.dev/badge/commands/anthropics/knowledge-work-plugins/fill-form/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/anthropics/knowledge-work-plugins/fill-form"><img src="https://agentmods.dev/badge/commands/anthropics/knowledge-work-plugins/fill-form.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.00010 | $0.00805 |
| Opus 5.5 | $0.00004 | $0.00322 |
| Sonnet 5.5 | $0.00002 | $0.00161 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
fill-form 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
If you need to check which tools are connected, see CONNECTORS.md.
Fill Form
Help the user complete a fillable PDF form in the live viewer. Unlike programmatic form tools, this gives the user direct visual feedback on every field as it's filled, with easy undo/edit in the viewer.
Why use this instead of programmatic form filling
- Visual confirmation — the user sees each value land in the right box, not just a success message
- Unnamed/unlabeled fields — many real-world PDFs have fields with
machine names like
Text1,Field_7, or no name at all. The label ("Date of Birth", "SSN") is printed next to the field on the rendered page, not in the field metadata. Useget_screenshotto see what each field actually is, then fill by name. - Easy correction — the user can edit or clear any field directly
in the viewer, or ask you to
fill_formagain with new values
Two approaches
User-driven (simple, well-labeled forms)
Call display_pdf with elicit_form_inputs: true. The server detects
form fields and prompts the user to enter values before the viewer
opens. The filled PDF is then displayed.
AI-assisted (complex forms, unnamed fields, or when you have context)
display_pdf(without elicit) — inspect returnedformFields(name, type, page, bounding box)- If field names are cryptic (
Text1,Field_7), useinteract→get_screenshotof each page with fields. Look at the visual labels next to each bounding box to understand what each field is. - For each field, either:
- Infer the value from conversation context (name, date, email)
- Ask the user, describing the field by its visual label ("the 'Date of Birth' box on page 1")
interact→fill_formwithfields: [{name, value}, ...]interact→get_screenshotof each filled page- Show the user, ask them to confirm or edit
Example
User: Help me fill out this W-9
You:
display_pdf→ formFields:f1_1,f1_2,f1_3,c1_1, ... (cryptic names)You:
interact→get_screenshotpage 1 → seef1_1is next to "Name",f1_2is "Business name",c1_1is the "Individual" checkboxYou: "I can see Name, Business name, Address, TIN, and tax classification checkboxes. I'll fill Name and Date from what I know — what's your TIN and business address?"
After answers:
interact→fill_form+get_screenshotYou: "Here's the filled form [screenshot]. The signature line is still blank — want to add your signature with
/pdf-viewer:sign?"
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 · 74 lines · 10 tokens per session scan A 787ca13d2032
fill-form is a command published in the GitHub repository anthropics/knowledge-work-plugins (32,712 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 805 once invoked, about $0.0000 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-09-05.
Other commands, from other repositories
open
Open a PDF in the in-app viewer panel.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
render-figures
Compile all .tex and .typ figure files in a directory.
docs
Document delivery with export to PPTX, DOCX, PDF formats.
pipeline-minutar-pdf
Pipeline completo de sentença judicial a partir de PDF (conversão, linha-tempo, relatório, análise, fundamentação, merge).