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-cellgit clone --depth 1 https://github.com/Ganbin/4d-development-skillWhat 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.00490 |
| Opus 5 | $0.00000 | $0.00245 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
vp-cell 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 2d 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
VP Cell ( vpAreaName : Text ; column : Integer ; row : Integer { ; sheet : Integer } ) : Object
| Parameter | Type | Description | |
|---|---|---|---|
| vpAreaName | Text | -> | 4D View Pro area form object name |
| column | Integer | -> | Column index |
| row | Integer | -> | Row index |
| sheet | Integer | -> | Sheet index (current sheet if omitted) |
| Result | Object | <- | Range object of a single cell |
Description
The VP Cell command returns a new range object referencing a specific cell.
This command is intended for ranges of a single cell. To create a range object for multiple cells, use the VP Cells command.
In vpAreaName, pass the name of the 4D View Pro area. If you pass a name that does not exist, an error is returned.
The column parameter defines the column of the cell range's position. Pass the column index in this parameter.
The row parameter defines the row of the cell range's position. Pass the row index in this parameter.
In the optional sheet parameter, you can indicate the index of the sheet where the range will be defined. If omitted or if you pass vk current sheet, the current spreadsheet is used by default.
indexing starts at 0.
Example
You want to define a range object for the cell shown below (on the current spreadsheet):
The code would be:
$cell:=VP Cell("ViewProArea";2;4) // C5
See also
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.
- 2d ago First seen · 56 lines · 0 tokens per session scan A 0fb0f90cb620
vp-cell 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 490 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
install
Install a skill from a local path, GitHub repository, npm package, or registry slug.
doctor
Run a system health check to diagnose common issues.
profile
Save, apply, and share multi-agent configuration profiles.
init
Scaffold a new SKILL.md for your agent skill.
setup
One command. All agents. Skills + MCP servers. Zero configuration.
diff
Compare two SKILL.md files section-by-section. Parses frontmatter and body sections independently, showing exactly what changed.