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.
npx agentmods add commands/ganbin/4d-development-skill/print-formgit clone --depth 1 https://github.com/Ganbin/4d-development-skillWrote 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/ganbin/4d-development-skill/print-form)<a href="https://agentmods.dev/commands/ganbin/4d-development-skill/print-form"><img src="https://agentmods.dev/badge/commands/ganbin/4d-development-skill/print-form.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02281 |
| Opus 5 | $0.00000 | $0.01141 |
| Sonnet 5 | $0.00000 | $0.00456 |
| Haiku 4.5 | $0.00000 | $0.00228 |
Grade A, and why
print-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 yesterday.
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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
| Parameter | Type | Description | |
|---|---|---|---|
| aTable | Table | → | Table owning the form, or Default table, if omitted |
| form | Text, Object | → | Name (string) of the form, or a POSIX path (string) to a .json file describing the form, or an object describing the form to print |
| formData | Object | → | Data to associate to the form |
| areaStart | Integer | → | Print marker, or Beginning area (if areaEnd is specified) |
| areaEnd | Integer | → | Ending area (if areaStart specified) |
| Function result | Integer | ← | Height of printed section |
Description
In the form parameter, you can pass:
- the name of a form, or
- the path (in POSIX syntax) to a valid .json file containing a description of the form to use (see Form file path), or
- an object containing a description of the form.
Since Print form does not issue a page break after printing the form, it is easy to combine different forms on the same page. Thus, Print form is perfect for complex printing tasks that involve different tables and different forms. To force a page break between forms, use the PAGE BREAK command. In order to carry printing over to the next page for a form whose height is greater than the available space, call the CANCEL command before the PAGE BREAK command.
Three different syntaxes may be used:
- Detail area printing
Syntax:
height:=Print form(myTable;myForm)
In this case, Print form only prints the Detail area (the area between the Header line and the Detail line) of the form.
- Form area printing
Syntax:
height:=Print form(myTable;myForm;marker)
In this case, the command will print the section designated by the marker. Pass one of the constants of the Form Area theme in the marker parameter:
| Constant | Type | Value |
|---|---|---|
| Form break0 | Integer | 300 |
| Form break1 | Integer | 301 |
| Form break2 | Integer | 302 |
| Form break3 | Integer | 303 |
| Form break4 | Integer | 304 |
| Form break5 | Integer | 305 |
| Form break6 | Integer | 306 |
| Form break7 | Integer | 307 |
| Form break8 | Integer | 308 |
| Form break9 | Integer | 309 |
| Form detail | Integer | 0 |
| Form footer | Integer | 100 |
| Form header | Integer | 200 |
| Form header1 | Integer | 201 |
| Form header10 | Integer | 210 |
| Form header2 | Integer | 202 |
| Form header3 | Integer | 203 |
| Form header4 | Integer | 204 |
| Form header5 | Integer | 205 |
| Form header6 | Integer | 206 |
| Form header7 | Integer | 207 |
| Form header8 | Integer | 208 |
| Form header9 | Integer | 209 |
- Section printing
Syntax:
height:=Print form(myTable;myForm;areaStart;areaEnd)
In this case, the command will print the section included between the areaStart and areaEnd parameters. The values entered must be expressed in pixels.
formData
Optionally, you can pass parameters to the form using either the formData object or the form class object automatically instantiated by 4D if you have associated a user class to the form. Any properties of the form data object will then be available from within the form context through the Form command. The form data object is available in the On Printing Detail form event.
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.
- yesterday First seen · 193 lines · 0 tokens per session scan A cc2ba29bc3bd
print-form is a command published in the GitHub repository Ganbin/4d-development-skill (9 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,281 tokens. 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-03.
Other commands, from other repositories
doctor
Run a system health check to diagnose common issues.
completions
Generate shell completion scripts for bash, zsh, and fish.
watch
Watch installed skills for file changes and auto-sync to agent directories.
automode-edit
Edit the project autoMode block in plain language. The agent interprets the request, builds a proposal, runs critique + hash gate, and writes atomically to .claude/settings.local.json.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.