← Back to Skills Marketplace
aholake

Expense Tracker

by Loc Vo · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
752
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install aholake-expense-tracker
Description
Track daily expenses in structured markdown files organized by month. Use when the user wants to log spending, view expense summaries, analyze spending patte...
README (SKILL.md)

Expense Tracker

Log and track daily expenses in markdown files organized by month.

Quick Start

Log an expense

python3 scripts/log_expense.py log \x3Camount> \x3Ccategory> [--description "text"] [--tags "tag1,tag2"] [--date YYYY-MM-DD]

Examples:

# Simple expense
python3 scripts/log_expense.py log 45000 Coffee

# With description
python3 scripts/log_expense.py log 250000 Dining --description "Lunch with team"

# With tags
python3 scripts/log_expense.py log 500000 Shopping --tags "clothes,sale" --description "New shirt"

# Specify date (for backdating)
python3 scripts/log_expense.py log 1200000 Vehicle --description "Gas" --date 2026-02-15

View monthly summary

# Current month
python3 scripts/log_expense.py summary

# Specific month
python3 scripts/log_expense.py summary 2026-02

# JSON output (for parsing)
python3 scripts/log_expense.py summary 2026-02 --json

File Organization

Expenses are stored in expenses/ directory at workspace root:

expenses/
├── 2026-01.md
├── 2026-02.md
└── 2026-03.md

Each file contains a markdown table:

# Expenses - 2026-02

| Date | Category | Amount (VND) | Description | Tags |
|------|----------|-------------|-------------|------|
| 2026-02-17 | Coffee | 45,000 | | |
| 2026-02-17 | Dining | 250,000 | Lunch with team | |
| 2026-02-17 | Shopping | 500,000 | New shirt | clothes,sale |

Categories

See references/categories.md for common expense categories. Use existing categories or create custom ones as needed.

Common categories:

  • Housing - Rent, utilities, home expenses
  • Vehicle - Gas, maintenance, parking
  • Dining - Restaurants, food delivery
  • Coffee - Cafes, coffee shops
  • Shopping - Clothes, electronics, general purchases
  • Entertainment - Movies, games, hobbies
  • Healthcare - Medicine, doctor visits
  • Subscriptions - Netflix, Spotify, gym, apps
  • Savings - Investments, emergency fund
  • Debt Payment - Loans, credit cards
  • Miscellaneous - Other expenses

Workflow Examples

Log daily expenses from conversation

When the user mentions spending money:

# User: "Just paid 35k for coffee"
python3 scripts/log_expense.py log 35000 Coffee

# User: "Grabbed lunch for 120k at Phở 24"
python3 scripts/log_expense.py log 120000 Dining --description "Phở 24"

# User: "Filled up gas, 400k"
python3 scripts/log_expense.py log 400000 Vehicle --description "Gas"

Monthly review

# Get summary
python3 scripts/log_expense.py summary 2026-02

# Read the expense file to see details
cat expenses/2026-02.md

Analyze spending patterns

# Get JSON for analysis
python3 scripts/log_expense.py summary 2026-02 --json

# Compare multiple months
python3 scripts/log_expense.py summary 2026-01 --json > jan.json
python3 scripts/log_expense.py summary 2026-02 --json > feb.json

Tips

  • Batch logging: User can tell you multiple expenses at once, log them all
  • Category consistency: Use the same category names to enable accurate summaries
  • Tags for filtering: Use tags for subcategories (e.g., "work", "weekend", "urgent")
  • Descriptions: Add context that helps identify the expense later
  • Regular reviews: Suggest monthly summaries to track spending patterns

Integration with Financial Goals

When tracking expenses, consider:

  1. Budget tracking: Compare monthly totals to target budget
  2. Spending patterns: Identify high-spend categories
  3. Emergency fund: Track savings progress
  4. Debt reduction: Monitor debt payment progress
  5. Financial ratios: Calculate expenses as % of income

Script Reference

log_expense.py

Commands:

  • log - Add an expense entry
  • summary - View monthly summary

Arguments (log):

  • amount - Amount in VND (required)
  • category - Category name (required)
  • --description/-d - Optional description
  • --tags/-t - Optional comma-separated tags
  • --date - Optional date (YYYY-MM-DD, defaults to today)
  • --workspace - Optional workspace path (defaults to ~/.openclaw/workspace)

Arguments (summary):

  • year_month - Optional YYYY-MM (defaults to current month)
  • --json - Output as JSON
  • --workspace - Optional workspace path

Output:

  • Creates/updates markdown files in expenses/ directory
  • Prints confirmation with file location
  • Summary shows total, count, and breakdown by category
Usage Guidance
This skill appears coherent and low-risk, but consider the following before installing: 1) The script stores expense data as plaintext markdown under a workspace (default: ~/.openclaw/workspace/expenses) — avoid storing sensitive account numbers. 2) You can pass --workspace to confine files to a project or sandbox; consider doing so. 3) The source/owner is unknown — you can manually review the short Python script (included) and run it locally to confirm behavior before allowing any automated invocation. 4) Because the agent can invoke skills autonomously by default, decide whether you want the agent to log expenses without explicit confirmation; otherwise invoke the skill manually. 5) Back up or protect the expenses directory if you care about privacy. Overall the code is short, readable, and consistent with the stated purpose.
Capability Analysis
Type: OpenClaw Skill Name: aholake-expense-tracker Version: 1.0.0 The skill is classified as suspicious due to a significant path traversal vulnerability in `scripts/log_expense.py`. The `--workspace` argument allows an attacker or a manipulated agent to specify an arbitrary directory for storing expense files, potentially leading to arbitrary file writes (e.g., `../../../etc/passwd.md`). While the `SKILL.md` does not explicitly instruct the agent to exploit this, the capability exists within the script. Additionally, user-provided `description` and `tags` are directly inserted into markdown files, posing a minor markdown injection risk. There is no evidence of intentional malicious behavior like data exfiltration, remote execution, or persistence mechanisms.
Capability Assessment
✓ Purpose & Capability
The name/description (expense logging, summaries, categories) match the included script and SKILL.md instructions. The skill asks for no unrelated credentials or binaries and only needs filesystem access to store markdown files under a workspace — this is proportionate to the stated purpose.
✓ Instruction Scope
Runtime instructions only run the bundled Python script (scripts/log_expense.py) to log or summarize expenses. The script reads/writes files under a workspace (default ~/.openclaw/workspace/expenses) and does not access network, other system configuration, or unrelated files. The SKILL.md and script explicitly document the optional --workspace override.
✓ Install Mechanism
There is no install specification (instruction-only plus a small bundled script). Nothing is downloaded or executed from external URLs, so installation risk is low.
✓ Credentials
The skill requests no environment variables or credentials. The script does not read secrets or external config; it only accepts an optional --workspace path argument. This is proportional to logging and summarizing expenses.
✓ Persistence & Privilege
always:false and no special privileges are requested. The only persistent effect is creating/updating markdown files in the chosen workspace directory (default under the user's home). The skill does not modify other skills or global agent configuration.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install aholake-expense-tracker
  3. After installation, invoke the skill by name or use /aholake-expense-tracker
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: Daily expense tracking with categories, tags, and monthly summaries
Metadata
Slug aholake-expense-tracker
Version 1.0.0
License —
All-time Installs 2
Active Installs 2
Total Versions 1
Frequently Asked Questions

What is Expense Tracker?

Track daily expenses in structured markdown files organized by month. Use when the user wants to log spending, view expense summaries, analyze spending patte... It is an AI Agent Skill for Claude Code / OpenClaw, with 752 downloads so far.

How do I install Expense Tracker?

Run "/install aholake-expense-tracker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Expense Tracker free?

Yes, Expense Tracker is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Expense Tracker support?

Expense Tracker is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Expense Tracker?

It is built and maintained by Loc Vo (@aholake); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments