Borrowing it
Nothing to install: this file belongs to HomenShum/NodeBenchAI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HomenShum/NodeBenchAI/main/.claude/skills/dep-vega/SKILL.mdgit clone --depth 1 https://github.com/HomenShum/NodeBenchAIWrote 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/skills/homenshum/nodebenchai/dep-vega)<a href="https://agentmods.dev/skills/homenshum/nodebenchai/dep-vega"><img src="https://agentmods.dev/badge/skills/homenshum/nodebenchai/dep-vega/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/homenshum/nodebenchai/dep-vega"><img src="https://agentmods.dev/badge/skills/homenshum/nodebenchai/dep-vega.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 71 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 99 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 72 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 100 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00080 | $0.01493 |
| Opus 5.5 | $0.00032 | $0.00597 |
| Sonnet 5.5 | $0.00016 | $0.00299 |
| Haiku 4.5 | $0.00008 | $0.00149 |
Grade A, and why
dep-vega 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vega ecosystem coordinated-bump runbook
Last verified
- Working versions (since 2026-04-26):
vega: ^6.2.0vega-lite: ^6.4.3vega-embed: ^7.1.0
- Schema URL in
SafeVegaChart.tsx:https://vega.github.io/schema/vega-lite/v6.json
Why these three move together
The vega family has tight peer-dependency coupling:
vega-litepeers onvega: ^6.0.0vega-embedpeers onvega: *andvega-lite: *(loose, but in practice tracks majors)- The Vega-Lite spec schema URL is version-locked in our component code
Bumping any one without the others either fails install (peer error) or runtime-fails when the schema URL doesn't match the installed Vega-Lite.
The 2026-04-26 bump in PR #124 was driven by CVE-2025-59840 — a HIGH XSS vulnerability via expression abuse with VEGA_DEBUG.toString calls, fixed in [email protected].
Coupled bumps (always do all three at once)
"vega": "^6.2.0",
"vega-embed": "^7.1.0",
"vega-lite": "^6.4.3"
Plus a schema URL update in code (see Recipe Step 3).
Recipe (bumping to a newer 6.x or 7.x)
Step 1 — Verify peer compatibility
npm view vega-lite@<target> peerDependencies # confirm "vega: ^6.0.0" range
npm view vega-embed@<target> peerDependencies # usually "vega: *", "vega-lite: *"
Step 2 — Bump all three in package.json
-"vega": "^6.2.0",
-"vega-embed": "^7.1.0",
-"vega-lite": "^6.4.3",
+"vega": "^6.X.0",
+"vega-embed": "^7.X.0",
+"vega-lite": "^6.X.0",
Then npm install.
Step 3 — Update spec schema URL (if vega-lite major changed)
If vega-lite major version changed (5 → 6 or 6 → 7), update the schema URL in SafeVegaChart.tsx:
- (spec as any).$schema = "https://vega.github.io/schema/vega-lite/v6.json";
+ (spec as any).$schema = "https://vega.github.io/schema/vega-lite/v7.json";
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.
- 1mo ago First seen · 128 lines · 80 tokens per session scan A 8c976f94a432
dep-vega is a skill published in the GitHub repository HomenShum/NodeBenchAI (15 stars, last pushed 3d ago), licensed MIT. It adds 80 tokens to every session and 1,493 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
convex-agents
Building AI agents with the Convex Agent component including thread management, tool integration, streaming responses, RAG patterns, and workflow orchestration.
convex-agents
Building AI agents with the Convex Agent component including thread management, tool integration, streaming responses, RAG patterns, and workflow orchestration.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
create-tech-design
Only use when the user explicitly invokes this skill by name.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…