house-inventory

house-inventory is a skill for Claude Code, Codex from kongaharsha/hermes_stack. It costs 15 tokens per session (546 once invoked), scanned A, original, MIT.

A home-inventory system that records physical items, the containers holding them, their locations, and reference photos. It can extract item descriptions from uploaded images or text and store the results in a structured Markdown file.

In plain words
What is it for?
Use it to catalog household items, identify what is inside boxes or bags, link reference photos, review extracted lists, and update the inventory file safely.
Why use it?
It replaces scattered notes with a container-based index that helps verify where items are stored. Review before saving helps catch incorrect descriptions or classifications.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for gbrain. Also seen: built for gbrain.

Good fit Use it to catalog household items, identify what is inside boxes or bags, link reference photos, review extracted lists, and update the inventory file safely.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kongaharsha/hermes_stack/house-inventory
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.

Any agent
npx skills add kongaharsha/hermes_stack --skill house-inventory
Clone the repo
git clone --depth 1 https://github.com/kongaharsha/hermes_stack

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for house-inventory

README.md
[![agentmods](https://agentmods.dev/badge/skills/kongaharsha/hermes_stack/house-inventory.svg)](https://agentmods.dev/skills/kongaharsha/hermes_stack/house-inventory)
Your own site
<a href="https://agentmods.dev/skills/kongaharsha/hermes_stack/house-inventory"><img src="https://agentmods.dev/badge/skills/kongaharsha/hermes_stack/house-inventory.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 546 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00015 $0.00546
Opus 5 $0.00008 $0.00273
Sonnet 5 $0.00003 $0.00109
Haiku 4.5 $0.00002 $0.00055

Measured 7d ago against content hash 0ee40d53f4b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

house-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 7d 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.

skills/house-inventory/SKILL.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

House Inventory

Overview

House Inventory is a disciplined system for cataloging physical assets, tracking container contents (boxes, bags, suitcases), and maintaining a verifiable index of reference imagery. Designed for precision, speed, and consistency.

Prerequisites

  • GBrain Setup: This skill requires an initialized gbrain environment. If you do not have one, set it up first: gbrain init or see GBrain Repository.
  • Inventory File: A valid markdown inventory file at the configured storage_path.

Workflow

  1. Cataloging: Extract objects/item descriptions from image uploads or manual text input.
  2. Container Indexing: Identify the source/target container (e.g., Box #1).
  3. Validation: Review extracted lists with the user to ensure terminology compliance before write operations.
  4. Persisting: Use structured patch operations to append or update entries while maintaining file integrity.

Format Principles

  • Container-First Hierarchy: Every item must belong to a defined container.
    ### Container: [Name]
    *   **Type:** [Box/Bag/Suitcase]
    *   **Location:** [Storage/Home]
    *   **Reference Photos:** [link1], [link2]
    *   **Items:** [Standardized bulleted list]
    

Standardized Terminology

  • Consistency: Use precise naming conventions (e.g., "Diyas" over "Mats").
  • Renaming: If descriptive terms are identified as inaccurate post-cataloging, perform an immediate refactor of the inventory entry to ensure future search accuracy.

Reliability Patterns

  • Atomic Patching: All modifications to the inventory file must be done via patch operations to prevent data loss.
  • Read-Before-Write: Must read current house-inventory.md state prior to execution to prevent conflicts with other agents.

Anti-Patterns

  • Hardcoded Pathing: Never assume absolute local file paths outside of the storage_path configuration.
  • Vision Guessing: Never assume item identity from low-confidence image analysis. If ambiguous, trigger a manual verification request to the user.
  • Cluttered Indexing: Do not create duplicate container entries; always verify existence before cataloging new items.

Read the full file on GitHub · 47 lines

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. 7d ago First seen · 47 lines · 15 tokens per session scan A 0ee40d53f4b6

Subscribe to this mod's changes

house-inventory is a skill published in the GitHub repository kongaharsha/hermes_stack (5 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 546 once invoked, about $0.0001 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.