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 skills add OneWave-AI/claude-skills --skill cowork-home-inventorygit clone --depth 1 https://github.com/OneWave-AI/claude-skillsWrote 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/onewave-ai/claude-skills/cowork-home-inventory)<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/cowork-home-inventory"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/cowork-home-inventory/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/onewave-ai/claude-skills/cowork-home-inventory"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/cowork-home-inventory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.00744 |
| Opus 5 | $0.00028 | $0.00372 |
| Sonnet 5 | $0.00011 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
cowork-home-inventory 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 12d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cowork Home Inventory
Build the document everyone wishes they had after the fire, flood, or break-in: a room-by-room inventory with values and proof. Input: a folder of photos (room shots, close-ups, serial-number shots) and receipts (PDF, email exports, images). Output: a structured inventory file plus a gap list of what still needs documenting.
Workflow
- Process the photos. Identify items in each image: what it is, brand/model when visible, condition, and the room (from filename, folder structure, or visual context). Read serial numbers and model plates from close-ups. Group multiple angles of the same item.
- Process the receipts. Extract item, vendor, date, and price from every receipt. Match receipts to photographed items where possible -- a matched receipt upgrades an item from "estimated" to "documented."
- Value the inventory. For receipt-matched items: purchase price and date. For unmatched items: estimated replacement cost (current retail for an equivalent, via web search for significant items), clearly labeled
ESTIMATE. Never present an estimate as a documented value. - Build the inventory. Output
home-inventory.csv(or .xlsx via the xlsx skill) -- room, item, brand/model, serial, purchase date, purchase price, replacement estimate, documentation status, photo filename(s), receipt filename -- plushome-inventory-summary.md: totals by room and category, the high-value items list, and overall documented vs. estimated ratio. - Gap list. What insurance will ask for that is missing: high-value items with no receipt (jewelry, electronics, instruments -- may need appraisals or serial-number photos), rooms with no coverage, items where only a wide shot exists. Rank by value at risk. Suggest the 20-minute photo walk that closes the worst gaps.
Rules
- Documented and estimated values never blend: every line is labeled, and the summary reports both totals separately.
- Never inflate. Replacement estimates use realistic current retail for equivalent items, not premium substitutes.
- Serial numbers are gold: capture every legible one, and put items that should have one but don't on the gap list.
- Do not catalog people, documents with financial account numbers, or anything in photos beyond the possessions themselves.
- Note policy-relevant thresholds generically ("many policies sub-limit jewelry; confirm your rider") without interpreting the user's actual policy -- unless the policy document is in the folder, in which case cite its stated limits next to the relevant categories.
- Keep the inventory file local and note in the summary that a copy belongs somewhere that survives the house (cloud drive, safe deposit).
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.
- 12d ago First seen · 39 lines · 55 tokens per session scan A 52643b63ef9a
cowork-home-inventory is a skill published in the GitHub repository OneWave-AI/claude-skills (291 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 744 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
pdf-text-replace
Replace text in fillable PDF forms by updating form field values. This skill should be used when users need to update names, addresses, dates, or other text in PDF form fields.
suede-product-marketing
Suede-owned product-marketing context discipline. Use when a project needs a shared record of product, audience, ICP, positioning, objections, customer language, proof, and goals, or when that record needs updating. NOT FOR: writing a campaign (use suede-campaign-in-a-box), conducting new customer interviews (use…
google-apps-script
Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a…
atelier-setup
Configure a repository for Atelier's development workflow. Use only when explicitly invoked; inspect existing guidance, issue-tracker and domain-document conventions, preview the proposed configuration, and write only after approval. It does not install Atelier or initialize external tooling.
text-stats
Compute word count, character count, or reading time for a piece of text using the in-bundle text-stats engine. Invoke whenever the user asks how long a passage is, how many words or characters it has, or how long it takes to read.
food-ppt
Turn a food & nutrition review report, evidence brief, or manuscript into a fully EDITABLE PowerPoint (.pptx) that opens in PowerPoint / Keynote / Google Slides with every title, bullet, table, and figure as a native editable object — nothing flattened to an image. Converts the outputs of food-research…