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/lianghsun/open-sheet/apply-commentsnpx skills add lianghsun/open-sheet --skill apply-commentsgit clone --depth 1 https://github.com/lianghsun/open-sheetWrote 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/lianghsun/open-sheet/apply-comments)<a href="https://agentmods.dev/skills/lianghsun/open-sheet/apply-comments"><img src="https://agentmods.dev/badge/skills/lianghsun/open-sheet/apply-comments.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 | $0.00070 | $0.00376 |
| Opus 5 | $0.00035 | $0.00188 |
| Sonnet 5 | $0.00014 | $0.00075 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
apply-comments 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.
What it actually says
Apply the comments left in the viewer
Notes left through the viewer's inspect mode are written into the workbook source as markers:
// @sheet-comment: this should be a percentage, and rounded to one decimal
col('margin', { header: 'Margin', formula: (r) => div(…) }),
Workflow
- Find them. Search
sheets/<id>/index.tsxfor@sheet-comment. If the user did not name a workbook, use thecurrent-sheetskill. - Read them all before changing anything. Two comments often describe one change, and a later one can contradict an earlier one.
- Apply each in the authoring layer. The comment sits next to the construct
it is about — a
col, adataentry, a<Cell>. Change that construct, not a coordinate. - Delete the marker once the edit is made. A stale marker gets re-applied next time and the edit lands twice.
- Ask, do not guess. If a comment is ambiguous ("this looks off"), leave the marker in place and ask what they meant. A wrong edit to a financial model is worse than an unapplied one.
After
Summarise what you changed, one line per comment, and name anything you left alone and why.
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 · 35 lines · 70 tokens per session scan A c0f39dd72517
apply-comments is a skill published in the GitHub repository lianghsun/open-sheet (120 stars, last pushed 9d ago), licensed MIT. It adds 70 tokens to every session and 376 once invoked, about $0.0003 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
excel-analyst-pro
Create or revise local Excel workbooks for DCF valuation, LBO returns, or budget-versus-actual variance analysis when the user explicitly requests a spreadsheet artifact. Use when evidence-backed finance models need reviewable formulas and checks. Trigger with explicit requests for a DCF, LBO, or variance workbook. Do…
excel-cli
Excel CLI automation skill for Windows workbooks. Use when a coding agent needs token-efficient, scriptable, or unattended Excel automation via excelcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk workbook edits. Supports Power Query, DAX, PivotTables, Tables, Ranges…
excel-mcp
Excel MCP Server skill for Windows workbook automation. Use when an assistant needs rich MCP tools to create, inspect, modify, format, or analyze Excel files. Supports Power Query (M), Data Model/DAX, PivotTables, Tables, Ranges, Charts, Slicers, formatting, screenshots, VBA macros, connections, and calculation mode.…
calc-spreadsheets
Use when creating, opening, or editing LibreOffice Calc ODS spreadsheets, or XLSX workbooks only when Excel compatibility is explicitly required.
npoi
Use when reading/writing Excel (.xls/.xlsx) or Word (.doc/.docx) files in .NET without Microsoft Office — data import/export, report generation, template filling. NPOI: .NET port of Apache POI for Office file I/O in server environments.
reogrid
Use when embedding an Excel-like spreadsheet control in .NET WinForms/WPF applications — formula engine, cell editing, clipboard, undo/redo. ReoGrid: .NET spreadsheet component with NPOI-based Excel read/write.