expense-categorization

expense-categorization is a skill for Claude Code from Receiptor-AI/bookkeeping-skills. It costs 71 tokens per session (1,992 once invoked), scanned A, original, MIT.

A bookkeeping tool that assigns business transactions to tax-related expense categories using vendor names, receipt details, and spending patterns. It can split one transaction across categories and learn from corrections.

In plain words
What is it for?
Use it to categorize transactions, inspect ambiguous purchases such as Amazon orders, split mixed expenses, and prepare records for tax reporting.
Why use it?
It reduces incorrect or overly broad expense labels, especially when a vendor sells many different kinds of items.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Good fit Use it to categorize transactions, inspect ambiguous purchases such as Amazon orders, split mixed expenses, and prepare records for tax reporting.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/receiptor-ai/bookkeeping-skills/expense-categorization
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 Receiptor-AI/bookkeeping-skills --skill expense-categorization
Clone the repo
git clone --depth 1 https://github.com/Receiptor-AI/bookkeeping-skills

Made for: Claude Code.

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 expense-categorization

README.md
[![agentmods](https://agentmods.dev/badge/skills/receiptor-ai/bookkeeping-skills/expense-categorization/github.svg)](https://agentmods.dev/skills/receiptor-ai/bookkeeping-skills/expense-categorization)
Your own site
<a href="https://agentmods.dev/skills/receiptor-ai/bookkeeping-skills/expense-categorization"><img src="https://agentmods.dev/badge/skills/receiptor-ai/bookkeeping-skills/expense-categorization/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.

agentmods 80×15 button for expense-categorization

Your own site · 80×15
<a href="https://agentmods.dev/skills/receiptor-ai/bookkeeping-skills/expense-categorization"><img src="https://agentmods.dev/badge/skills/receiptor-ai/bookkeeping-skills/expense-categorization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,992 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.00071 $0.01992
Opus 5 $0.00036 $0.00996
Sonnet 5 $0.00014 $0.00398
Haiku 4.5 $0.00007 $0.00199

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

Security

Grade A, and why

expense-categorization 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 10d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/category_review_summary.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/expense-categorization/SKILL.md · 171 lines

How it starts

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

Expense Categorization

Assign every transaction to the correct expense category so it flows to the right line on a tax return, produces accurate financial statements, and survives an audit.

Read these when needed

  • Read references/DECISION-RULES.md when deciding whether a category is safe to auto-assign or should go to review.
  • Run scripts/category_review_summary.py when you already have categorized records and need a deterministic summary by confidence, category, and review status.

Why categorization matters

The IRS doesn't audit "total expenses." It audits individual line items on Schedule C (or the equivalent form for your entity type). A business that lumps everything into "Other Expenses" invites scrutiny. Proper categorization also reveals spending patterns — you can't cut costs you can't see.

For the full Schedule C line-by-line reference (Lines 8–27a with what belongs and what doesn't), see the schedule-c-categories skill.

Categorization logic

Primary signal: vendor name

Most categorization comes from the vendor name alone. Use the mapping table below to auto-categorize high-confidence vendors.

Secondary signal: line items

When the vendor is ambiguous (Amazon, Walmart, Costco), look at line items from the receipt. This is where high-quality extraction is especially useful — line items matter more than totals. Amazon with "USB-C Hub, Monitor Stand" → Equipment. Amazon with "Paper Towels, Hand Soap" → Office Supplies. Mixed orders should be split across categories.

Tertiary signal: amount patterns

Recurring monthly charges at the same amount → likely Software & Subscriptions (Line 27a). Round-number transfers to individuals → likely Contractors (Line 11). Small charges at restaurants → Meals (Line 24b).

Learning from corrections

When the user corrects a categorization, store that mapping. User-confirmed mappings should override default logic going forward.

High-confidence vendor mapping (auto-categorize)

Read the full file on GitHub · 171 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 171 lines · 71 tokens per session scan A dcd96a022990

Subscribe to this mod's changes

expense-categorization is a skill published in the GitHub repository Receiptor-AI/bookkeeping-skills (4 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 1,992 once invoked, about $0.0004 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.