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/warroom-ceo/core/reconciliationnpx skills add WARROOM-CEO/CORE --skill reconciliationgit clone --depth 1 https://github.com/WARROOM-CEO/COREWrote 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/warroom-ceo/core/reconciliation)<a href="https://agentmods.dev/skills/warroom-ceo/core/reconciliation"><img src="https://agentmods.dev/badge/skills/warroom-ceo/core/reconciliation.svg" alt="Measured on agentmods" height="20"></a>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.00063 | $0.01760 |
| Opus 5 | $0.00032 | $0.00880 |
| Sonnet 5 | $0.00013 | $0.00352 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
reconciliation-th 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 5d 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.
This is a copy
94% identical to reconciliation — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Language: All user-facing output — responses, summaries, and any text the user will read — must be written in Thai (ภาษาไทย). Internal logic, file paths, code snippets, and technical values remain in English.
Reconciliation
Important: This skill assists with reconciliation workflows but does not provide financial advice. All reconciliations should be reviewed by qualified financial professionals before sign-off.
Methodology and best practices for account reconciliation, including GL-to-subledger, bank reconciliations, and intercompany. Covers reconciling item categorization, aging analysis, and escalation.
Reconciliation Types
GL to Subledger Reconciliation
Compare the general ledger control account balance to the detailed subledger balance.
Common accounts:
- Accounts receivable (GL control vs AR subledger aging)
- Accounts payable (GL control vs AP subledger aging)
- Fixed assets (GL control vs fixed asset register)
- Inventory (GL control vs inventory valuation report)
- Prepaid expenses (GL control vs prepaid amortization schedule)
- Accrued liabilities (GL control vs accrual detail schedules)
Process:
- Pull GL balance for the control account as of period end
- Pull subledger trial balance or detail report as of the same date
- Compare totals — they should match if posting is real-time
- Investigate any differences (timing of posting, manual entries not reflected, interface errors)
Common causes of differences:
- Manual journal entries posted to the control account but not reflected in the subledger
- Subledger transactions not yet interfaced to the GL
- Timing differences in batch posting
- Reclassification entries in the GL without subledger adjustment
- System interface errors or failed postings
Bank Reconciliation
Compare the GL cash balance to the bank statement balance.
Process:
- Obtain the bank statement balance as of period end
- Pull the GL cash account balance as of the same date
- Identify outstanding checks (issued but not cleared at the bank)
- Identify deposits in transit (recorded in GL but not yet credited by bank)
- Identify bank charges, interest, or adjustments not yet recorded in GL
- Reconcile both sides to an adjusted balance
What ships with it
1 file 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.
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.
- 5d ago First seen · 178 lines · 63 tokens per session scan A b1808903b543
reconciliation-th is a skill published in the GitHub repository WARROOM-CEO/CORE (30 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,760 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to reconciliation, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
sector-rotation
行业轮动分析——申万行业景气度评分、行业动量排名、产业链传导、估值/盈利/资金流多维比较框架.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
chenhao-limit-up
Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
vectorbt
High-performance vectorized backtesting with parameter optimization, portfolio simulation, and rich performance metrics.