A tool for entering values into fillable PDF forms while viewing the document and checking where each value goes.

Use it to complete applications, questionnaires, and other fillable PDF documents.

It helps with forms whose fields are unclear, unnamed, or poorly described in the PDF's internal data. You can visually check entries and correct them in the viewer.

fill-form — Command for Claude Code by sun2443/designer-skills

Install

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.

Clone the repo

git clone --depth 1 https://github.com/sun2443/designer-skills

agentmods

npx agentmods add commands/sun2443/designer-skills/fill-form

Made for: Claude Code.

Or install pdf-viewer, 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sun2443/designer-skills/fill-form/github.svg)](https://agentmods.dev/commands/sun2443/designer-skills/fill-form)

Your own site

<a href="https://agentmods.dev/commands/sun2443/designer-skills/fill-form"><img src="https://agentmods.dev/badge/commands/sun2443/designer-skills/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sun2443/designer-skills/fill-form"><img src="https://agentmods.dev/badge/commands/sun2443/designer-skills/fill-form.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 805 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 100% copy Near-identical to another mod 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.

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

Measured 13d ago against content hash 787ca13d2032, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 13d 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.

Origin

This is a copy

100% identical to fill-form — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

pdf-viewer/commands/fill-form.md · 74 lines

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. Use get_screenshot to 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_form again 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 returned formFields (name, type, page, bounding box)
If field names are cryptic (Text1, Field_7), use interact → get_screenshot of 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_form with fields: [{name, value}, ...]
interact → get_screenshot of 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_screenshot page 1 → see f1_1 is next to "Name", f1_2 is "Business name", c1_1 is the "Individual" checkbox

You: "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_screenshot

You: "Here's the filled form [screenshot]. The signature line is still blank — want to add your signature with /pdf-viewer:sign?"

Read the full file on GitHub · 74 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.

13d ago First seen · 74 lines · 10 tokens per session scan A 787ca13d2032

Subscribe to this mod's changes

fill-form is a command published in the GitHub repository sun2443/designer-skills (0 stars, last pushed 6mo ago), 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. It is 100% identical to fill-form, differing in 0 lines, and is treated as a copy.

Documents PDF

fill-form

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Fill Form

Why use this instead of programmatic form filling

Two approaches

User-driven (simple, well-labeled forms)

AI-assisted (complex forms, unnamed fields, or when you have context)

Example

What this file has done since we first saw it

Other commands, from other repositories

open

brief-compliance-check

render-figures

docs

pipeline-minutar-pdf

cti-report