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/eigenweltlabs/legalworkWrote 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/eigenweltlabs/legalwork/fill-form)<a href="https://agentmods.dev/commands/eigenweltlabs/legalwork/fill-form"><img src="https://agentmods.dev/badge/commands/eigenweltlabs/legalwork/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/eigenweltlabs/legalwork/fill-form"><img src="https://agentmods.dev/badge/commands/eigenweltlabs/legalwork/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.00016 | $0.00308 |
| Opus 5 | $0.00008 | $0.00154 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
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 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
Fill a PDF form (AcroForm) with AI — the user reviews the filled copy in the in-app PDF viewer. The original file is never modified.
Load and follow the pdf-tools skill, then carry out this request:
$ARGUMENTS
Reminders from the skill:
inspectthe PDF first — it lists every form field's exactname,type, current value, and (for dropdowns/radios) the validoptions. Fill by those exact names; choice fields only accept one of their listed options.- Run the
fillsubcommand with one JSON object of{ "fieldName": value }— it writes<name>.filled.pdfnext to the source. - If
inspectshowsfields: [], the PDF has no fillable form (likely a flat scan) — say so plainly and offer/annotateinstead; don't pretend to fill it. - Never invent a value the user didn't give — ask for anything missing.
- Flag every
skippedentry with its reason and retry with corrected names/options. - End your reply with the output
namethe tool returns on its own line so the filled copy surfaces as a clickable PDF artifact in the panel.
If no PDF is named in the arguments, ask which form to fill first.
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 · 27 lines · 16 tokens per session scan A 459937e2b686
fill-form is a command published in the GitHub repository eigenweltlabs/legalwork (103 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 308 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-30.
Other commands, from other repositories
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.
pipeline-minutar-pdf
Pipeline completo de sentença judicial a partir de PDF (conversão, linha-tempo, relatório, análise, fundamentação, merge).
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
docs
Document delivery with export to PPTX, DOCX, PDF formats.
cheatsheet
Generate a one-page exam cheatsheet from course-index and errors/log.md. Outputs to cheatsheet/final.md. Optionally convert to PDF.
render-figures
Compile all .tex and .typ figure files in a directory.