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 skills/homenshum/nodebenchai/dep-xlsxnpx skills add HomenShum/NodeBenchAI --skill dep-xlsxgit 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-xlsx)<a href="https://agentmods.dev/skills/homenshum/nodebenchai/dep-xlsx"><img src="https://agentmods.dev/badge/skills/homenshum/nodebenchai/dep-xlsx.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.00095 | $0.01870 |
| Opus 5 | $0.00048 | $0.00935 |
| Sonnet 5 | $0.00019 | $0.00374 |
| Haiku 4.5 | $0.00010 | $0.00187 |
Grade A, and why
dep-xlsx 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 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.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
xlsx (SheetJS) remediation runbook
Last verified
- Working pin:
https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz(held since 2026-04-26) - Known-bad:
xlsx@^0.18.5from npm registry (2 HIGH CVEs, no upstream fix)
Why we use a CDN tarball
Two HIGH CVEs against the npm-published xlsx:
CVE-2024-22363— ReDoS in SheetJSCVE-2023-30533— Prototype Pollution in SheetJS
Neither has a fix on the npm registry. SheetJS moved to publishing fixed releases through their own CDN at cdn.sheetjs.com. The npm version of the package is no longer updated by the maintainers. Their official remediation guidance is to install from the CDN tarball.
Closed by PR #124.
Alternatives evaluated (and rejected)
| Option | Why rejected |
|---|---|
@e965/xlsx (community fork on npm) |
Published by individual e965 ([email protected]) from e965/sheetjs-npm-publisher. Supply-chain risk: unknown maintainer. |
Migrate to exceljs |
Different API (async streams, 1-indexed cells), 4-8 hours of careful refactoring across 4 files in src/features/documents/, 200KB+ bundle weight increase. No security benefit (CDN already addresses the CVEs). |
Migrate to read-excel-file |
Read-only, doesn't cover the editor/writer paths in SpreadsheetMiniEditor.tsx and SpreadsheetView.tsx. Same migration effort as exceljs but lower coverage. |
xlsx-js-style (community fork with styles) |
Same supply-chain concern as @e965/xlsx. |
| Wrap usage with input validation | Defensive but doesn't make alerts go away. |
Recipe (when bumping to a newer SheetJS CDN release)
When SheetJS publishes a new version (check https://cdn.sheetjs.com/):
- Update
package.json:-"xlsx": "https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz", +"xlsx": "https://cdn.sheetjs.com/xlsx-0.20.X/xlsx-0.20.X.tgz", npm installnpx tsc --noEmit— should be clean (xlsx API has been stable for years)npx vite build— must succeed- Manual smoke: open a
.xlsxfile in the documents preview/editor surfaces and verify it renders + saves correctly
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 · 132 lines · 95 tokens per session scan A 1663b8686cf6
dep-xlsx is a skill published in the GitHub repository HomenShum/NodeBenchAI (14 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 1,870 once invoked, about $0.0005 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-30.
Other skills, from other repositories
gog-workspace
Use the gog CLI for Google Workspace tasks across Gmail, Calendar, Drive, Docs, Sheets, Contacts, and related services. Use when the user asks to check email, search Gmail, inspect calendar events, find Drive files, read Docs or Sheets, or manage Google Workspace data through gog.
xlsx
Create and edit Excel .xlsx workbooks (sheets, cells, formulas, formatting) via Python openpyxl. Use to generate spreadsheets or write/update cells. Reading is via os.fs.readdocument.
Workspace Data Analyst
Analyze CSV files in the workspace and summarize insights.
meter-invoice
Generate CocoMeter chargeback invoices. Usage: $meter invoice.
xlsx
Read and extract cell data from .xlsx Excel spreadsheets as TSV. Use when the user uploads or references an Excel file to read or summarize.
spreadsheet-agent
Authoring playbook for building agents that read or write tabular data — Google Sheets, Microsoft Excel, CSV, Airtable, Notion databases, or any spreadsheet. Use this when the user wants an agent that updates rows, reads cells, computes totals, generates reports from sheets, syncs data between spreadsheets, or…