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-get-table-column-indexgit 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-get-table-column-index)<a href="https://agentmods.dev/commands/ganbin/4d-development-skill/vp-get-table-column-index"><img src="https://agentmods.dev/badge/commands/ganbin/4d-development-skill/vp-get-table-column-index.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.00487 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade C, and why
vp-get-table-column-index scanned grade C with 1 finding 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 5d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- REF #_method_.VP Get table column index.Syntax --> What it actually says
| Release | Changes |
|---|---|
| 19 R7 | Added |
VP Get table column index ( vpAreaName : Text ; tableName : Text ; columnName : Text {; sheet : Integer } ) : Integer
| Parameter | Type | Description | |
|---|---|---|---|
| vpAreaName | Text | -> | 4D View Pro area form object name |
| tableName | Text | -> | Table name |
| columnName | Text | -> | Name of the table column |
| sheet | Integer | -> | Sheet index (current sheet if omitted) |
| Result | Integer | <- | Index of columnName |
Description
The VP Get table column index command returns the index of the columnName in the tableName.
In vpAreaName, pass the name of the 4D View Pro area.
In columnName, pass the name of the table column for which you want to get the index.
In sheet, pass the index of the target sheet. If no index is specified or if you pass -1, the command applies to the current sheet.
Indexing starts at 0.
If tableName or columnName is not found, the command returns -1.
Example
// Search the column id according the column name
var $id : Integer
$id:=VP Get table column index($area; $tableName; "Weight price")
// Remove the column by id
VP REMOVE TABLE COLUMNS($area; $tableName; $id)
See also
VP CREATE TABLE VP Find table VP Get table column attributes VP SET TABLE COLUMN ATTRIBUTES
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.
- 5d ago First seen · 58 lines · 0 tokens per session scan C cdf574dccb28
vp-get-table-column-index 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 487 tokens. A static security scan graded it C with 1 finding (hidden instructions). 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.