gsv-kit-pointer

A repository rule that points shared VDT kit files to a separate GSV folder and keeps this repository focused on PoolAI product files.

In plain words
What is it for?
Finding the canonical shared kit, choosing between PoolAI and GSV work, and handling the repository's project-specific documents.
Why use it?
It prevents shared rules and product-specific material from becoming mixed or duplicated.

Cursor rule for Cursor

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 rules/platinoff/poolai/gsv-kit-pointer
Clone the repo
git clone --depth 1 https://github.com/platinoff/poolAI

Made for: Cursor.

Per session 227 This file is loaded in full into every session.
When invoked 227 The same file — it is already loaded in full.
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.00227 $0.00227
Opus 5 $0.00113 $0.00113
Sonnet 5 $0.00045 $0.00045
Haiku 4.5 $0.00023 $0.00023

Measured yesterday against content hash 08afca5ea676, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gsv-kit-pointer 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.

.cursor/rules/gsv-kit-pointer.mdc · 17 lines

What it actually says

Kit pointer (PoolAI)

Git-канон спільного VDT (rules, marketplace skills, абракадабра host) — S:\rust\GSV. Open that folder or S:\rust\GSV\gsv.code-workspace.

This repo keeps product canon only: FM, concept, cargo test-ci, Playwright admin, OpenAPI gap, Galaxy, 90–95% ratio, poolai-documentation.

When the owner writes абракадабра here: still AskQuestion poolai | gsv, then follow .agents/skills/abracadabra/SKILL.md (fallback copy). Prefer draining from the GSV window.

Canon: S:/rust/GSV/docs/gsv/GSV_VDT_KIT.md · registry S:/rust/GSV/docs/gsv/PRODUCTS.md.

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. yesterday First seen · 17 lines · 227 tokens per session scan A 08afca5ea676

Subscribe to this mod's changes

gsv-kit-pointer is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed 8d ago), licensed MIT. It adds 227 tokens to every session, about $0.0011 per session on Opus 5. 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.