vp-export-to-object

vp-export-to-object is a command for coding agents from Ganbin/4d-development-skill. It costs 0 tokens per session (575 once invoked), scanned A, original, MIT.

A command for exporting a 4D View Pro spreadsheet area—the spreadsheet component used in 4D applications—as an object. The result can include formatting and current data values.

In plain words
What is it for?
Use it to save a spreadsheet area in a 4D database object field or prepare it for further conversion.
Why use it?
It lets an application capture the spreadsheet’s contents and settings in a form that can be stored or processed.

Command

Install

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.

agentmods
npx agentmods add commands/ganbin/4d-development-skill/vp-export-to-object
Clone the repo
git clone --depth 1 https://github.com/Ganbin/4d-development-skill

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.

agentmods badge for vp-export-to-object

README.md
[![agentmods](https://agentmods.dev/badge/commands/ganbin/4d-development-skill/vp-export-to-object.svg)](https://agentmods.dev/commands/ganbin/4d-development-skill/vp-export-to-object)
Your own site
<a href="https://agentmods.dev/commands/ganbin/4d-development-skill/vp-export-to-object"><img src="https://agentmods.dev/badge/commands/ganbin/4d-development-skill/vp-export-to-object.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 575 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00575
Opus 5 $0.00000 $0.00287
Sonnet 5 $0.00000 $0.00115
Haiku 4.5 $0.00000 $0.00057

Measured 3d ago against content hash 66862918b3e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vp-export-to-object 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 3d 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.

docs/ViewPro/commands/vp-export-to-object.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

VP Export to object ( vpAreaName : Text {; options : Object} ) : Object

Parameter Type Description
vpAreaName Text -> 4D View Pro area form object name
options Object -> Export options
Result Object <- 4D View Pro object

Description

The VP Export to object command returns the 4D View Pro object attached to the 4D View Pro area vpAreaName. You can use this command for example to store the 4D View Pro area in a 4D database object field.

In vpAreaName, pass the name of the 4D View Pro area. If you pass a name that does not exist, an error is returned.

In the options parameter, you can pass the following export options, if required:

Property Type Description
includeFormatInfo Boolean True (default) to include formatting information, false otherwise. Formatting information is useful in some cases, e.g. for export to SVG. On the other hand, setting this property to False allows reducing export time.
includeBindingSource Boolean True (default) to export the current data context values as cell values in the exported object (data contexts themselves are not exported). False otherwise. Cell binding is always exported.

For more information on 4D View Pro objects, please refer to the 4D View Pro object paragraph.

Example 1

You want to get the "version" property of the current 4D View Pro area:

var $vpAreaObj : Object
var $vpVersion : Number
$vpAreaObj:=VP Export to object("vpArea")
 // $vpVersion:=OB Get($vpAreaObj;"version")
$vpVersion:=$vpAreaObj.version

Example 2

You want to export the area, excluding formatting information:

var $vpObj : Object
$vpObj:=VP Export to object("vpArea";New object("includeFormatInfo";False))

See also

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

  1. 3d ago First seen · 59 lines · 0 tokens per session scan A 66862918b3e5

Subscribe to this mod's changes

vp-export-to-object 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 575 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.