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/vp-export-to-blobgit 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/vp-export-to-blob)<a href="https://agentmods.dev/commands/ganbin/4d-development-skill/vp-export-to-blob"><img src="https://agentmods.dev/badge/commands/ganbin/4d-development-skill/vp-export-to-blob.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.1 | $0.00000 | $0.00783 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
vp-export-to-blob 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 6d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VP EXPORT TO BLOB ( vpAreaName : Text ; paramObj : Object )
| Parameter | Type | Description | |
|---|---|---|---|
| vpAreaName | Text | -> | 4D View Pro area form object name |
| paramObj | Object | -> | Export options |
Description
The VP EXPORT TO BLOB command exports the vpAreaName 4D View Pro document in a 4D.Blob according to the paramObj options. The exported blob is available through the export callback. Exporting and importing 4D View Pro areas as blobs is fast and memory-efficient.
In paramObj, you can pass several properties:
| Property | Type | Description |
|---|---|---|
| formula | 4D.Function | (mandatory) Callback method to be launched when the export has completed. See Passing a callback method (formula). |
| includeAutoMergedCells | Boolean | Whether to include the automatically merged cells when saving, default=false. |
| includeBindingSource | Boolean | Whether to include the binding source when saving, default=true. |
| includeCalcModelCache | Boolean | Whether to include the extra data of calculation. Can impact the speed of opening the file, default=false. |
| includeEmptyRegionCells | Boolean | Whether to include any empty cells(cells with no data or only style) outside the used data range, default=true |
| includeFormulas | Boolean | Whether to include the formula when saving, default=true. |
| includeStyles | Boolean | Whether to include the style when saving, default=true. |
| includeUnusedNames | Boolean | Whether to include the unused custom name when saving, default=true. |
| saveAsView | Boolean | Whether to apply the format string to exporting value when saving, default=false. |
The following parameters can be used in the callback method:
| Parameter | Type | Description | |
|---|---|---|---|
| param1 | text | The name of the 4D View Pro object | |
| param2 | 4D.Blob | The exported blob | |
| param3 | object | A reference to the command's paramObj parameter | |
| param4 | object | An object returned by the method with a status message | |
| .success | boolean | True if export with success, False otherwise. | |
| .errorCode | integer | Error code. | |
| .errorMessage | text | Error message. |
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.
- 6d ago First seen · 76 lines · 0 tokens per session scan A 31e314ad8e4b
vp-export-to-blob 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 783 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.