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/saolalab/clawforce/bookkeepingnpx skills add saolalab/clawforce --skill bookkeepinggit clone --depth 1 https://github.com/saolalab/clawforceWhat 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.00032 | $0.01368 |
| Opus 5 | $0.00016 | $0.00684 |
| Sonnet 5 | $0.00006 | $0.00274 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
bookkeeping 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 2d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bookkeeping
Chart of Accounts Template
Maintain a standardized chart of accounts organized by category:
Assets
- 1000-1999: Current Assets
- 1010: Cash - Operating Account
- 1020: Cash - Reserve Account
- 1100: Accounts Receivable
- 1200: Prepaid Expenses
- 1300: Inventory (if applicable)
- 2000-2999: Fixed Assets
- 2010: Equipment
- 2020: Accumulated Depreciation - Equipment
- 2100: Software Licenses
- 2200: Accumulated Amortization - Software
Liabilities
- 3000-3999: Current Liabilities
- 3010: Accounts Payable
- 3020: Accrued Expenses
- 3030: Short-term Debt
- 3100: Deferred Revenue
- 4000-4999: Long-term Liabilities
- 4010: Long-term Debt
- 4100: Lease Obligations
Equity
- 5000-5999: Equity
- 5010: Common Stock
- 5020: Additional Paid-in Capital
- 5100: Retained Earnings
Revenue
- 6000-6999: Revenue
- 6010: Product Revenue
- 6020: Service Revenue
- 6100: Other Income
Expenses
- 7000-7999: Cost of Goods Sold
- 7010: Cost of Revenue
- 7100: Infrastructure Costs
- 8000-8999: Operating Expenses
- 8010: Salaries & Wages
- 8020: Benefits
- 8100: Rent
- 8200: Utilities
- 8300: Marketing & Advertising
- 8400: Professional Services (Legal, Accounting)
- 8500: Software & Subscriptions
- 8600: Travel & Entertainment
- 8700: Office Supplies
- 8800: Insurance
- 8900: Depreciation & Amortization
- 9000-9999: Other Expenses
- 9010: Interest Expense
- 9100: Taxes
Journal Entry Format
Record all transactions using double-entry bookkeeping:
### Journal Entry: {Description}
- **Date**: YYYY-MM-DD
- **Reference**: {Invoice # / Transaction ID}
- **Debit Account**: {Account Code} - {Account Name} | Amount: $X
- **Credit Account**: {Account Code} - {Account Name} | Amount: $X
- **Description**: {Detailed explanation}
- **Approved By**: {Name}
Example:
### Journal Entry: Monthly SaaS Subscription
- **Date**: 2026-02-01
- **Reference**: INV-2026-001
- **Debit Account**: 8500 - Software & Subscriptions | Amount: $500
- **Credit Account**: 3010 - Accounts Payable | Amount: $500
- **Description**: Monthly subscription for cloud infrastructure tools
- **Approved By**: Finance Controller
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.
- 2d ago First seen · 182 lines · 32 tokens per session scan A 1f49f1879354
bookkeeping is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 1,368 once invoked, about $0.0002 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
daily-deep-brief
8 点这个时点：HK 开盘前 90 分钟，US 已收盘 4 小时。盘前是 deep think 最好的窗口 — 有完整夜间消息面，没有盘中执行压力。.
financial-expense-automation
当用户上传 PDF、JPG、JPEG、PNG 附件，或消息中包含"报销""发票""票据""录入""火车票""机票"等关键词时触发。对附件内容进行识别，若确认为报销票据则提取结构化字段并写入飞书多维表格；若识别后内容不是报销票据，告知用户并终止流程。.
hk-stock-analysis
Workspace-aware Hong Kong stock analysis for kcn. Routes through clawock analyze-hk (Tencent primary + Eastmoney full-batch independent cross-check/fallback → stooq → yfinance) for price/技术指标/news, layered with HK-specific concepts — 南向资金, HSTECH 方向, 杠杆 ETF 衰减, 老千股警惕, T+0 无涨跌幅. Use when user asks about a HK ticker…
us-stock-analysis
Workspace-aware US stock analysis for kcn. Routes through clawock analyze-us / clawock us-quotes instead of generic web search, then layers fundamental/technical/news analysis on top. Use when user asks to analyze a US ticker (e.g. "analyze AAPL", "look at RKLB", "compare TSLA vs NVDA"), check earnings, run…
crypto-monitor
定期巡检加密货币行情，通过 CoinGecko API 获取 BTC、ETH、LTC 的实时价格（USD/CNY） 和 24h 涨跌幅。涨跌幅超过阈值时推送行情摘要，全部正常时回复 HEARTBEATOK。 支持 /crypto-monitor 斜杠命令触发，也可通过自然语言触发（如"帮我看一下 BTC 行情"、 "加密货币价格怎么样"、"crypto price check"）。 配合 Cron 定时任务实现自动巡检。.
portfolio-swarm-review
Multi-agent swarm review of kcn's current holdings. Inspired by TauricResearch/TradingAgents framework already in workspace — three-tier analysis (analysts → bull/bear debate → risk debate + judge) with confidence scoring. Use for post-close reviews, holiday/next-session planning, pre-add sizing decisions, and any…