Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/cynco-labs/ai-accounting-skillsnpx agentmods add skills/cynco-labs/ai-accounting-skills/journal-entriesWrote 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/cynco-labs/ai-accounting-skills/journal-entries)<a href="https://agentmods.dev/skills/cynco-labs/ai-accounting-skills/journal-entries"><img src="https://agentmods.dev/badge/skills/cynco-labs/ai-accounting-skills/journal-entries/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.
<a href="https://agentmods.dev/skills/cynco-labs/ai-accounting-skills/journal-entries"><img src="https://agentmods.dev/badge/skills/cynco-labs/ai-accounting-skills/journal-entries.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.00522 |
| Opus 5 | $0.00019 | $0.00261 |
| Sonnet 5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
journal-entries 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 12d 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.
What it actually says
/journal-entries
Purpose
Convert classified activity into double-entry journals. Main job: post. Engine posts; agent judges openings/exceptions.
Load shared/kernel-contract.md and shared/guardrails.md.
Step 1 — Post (required)
python3 scripts/post_journals.py \
--client-dir <client> \
--bank-code 1000 \
--opening-from-bank
# or with explicit openings pack
python3 scripts/post_journals.py \
--transactions workpapers/transactions.json \
--output workpapers/journals.json \
--openings workpapers/journals_opening.json \
--bank-code 1000
npx @cynco/accounting-skills post <client> --opening-from-bank
| Input | Rule |
|---|---|
Classified transactions.json |
Every line has account_code (or fail) |
| Inflow | DR bank · CR code |
| Outflow | DR code · CR bank |
| Openings | --openings file or --opening-from-bank (equity offset) |
Prefer the script over line-by-line chat postings (scripts).
Done when: journals.json written and every JE balances (script exit 0).
Step 2 — Roll preliminary TB (required)
python3 scripts/roll_tb.py --client-dir <client> --preliminary
npx @cynco/accounting-skills tb <client> --preliminary
TB totals only via roll_tb — never typed by the agent.
Done when: tb_preliminary.json exists and difference == 0 (or must stop recorded).
Manual / non-bank journals
Client-supplied or payroll/sales books: append balancing JEs to journals.json (same schema), then re-run roll_tb. Each JE must balance or the roll fails.
Gates
- Every JE: Σ DR = Σ CR
- No blank accounts
- Prelim TB difference = 0
Output
workpapers/journals.json + workpapers/tb_preliminary.json.
Next: bank recon → YE → roll_tb --adjusted.
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.
- 12d ago First seen · 71 lines · 39 tokens per session scan A b1e3b9cd6d3b
journal-entries is a skill published in the GitHub repository cynco-labs/ai-accounting-skills (3 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 522 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-31.
Other skills, from other repositories
countbean-accounting
Rules for writing correct double-entry Beancount transactions when managing a Countbean cloud book — account naming, how to balance postings, categorisation, and safe ingestion. Use whenever recording, importing, or correcting financial data in a Countbean book.
bookkeeping
Use when a small business needs audit-ready books — a chart of accounts, posting a transaction to the right account and side, clearing an uncategorized bank feed, cash vs accrual, or a ledger that won't tie to the bank. NOT interpreting the numbers — runway, burn, P&L cadence (that is finance-ops), NOT issuing…
jangbu-jongso
A Korean tax-document checklist generator for individuals, freelancers, sole-company owners, mixed earners, and certain business owners.
korean-jangbu-for
A Korean bookkeeping assistant for startups, freelancers, sole proprietors, and one-person companies. It processes financial files locally, helps classify transactions, and prepares accounting and tax outputs.
jangbu-import
A data-import workflow for turning bank files, card records, spreadsheets, receipts, tax invoices, and statement PDFs into a standard set of 13 transaction fields. OCR, or optical character recognition, is used to read information from document images and PDFs.
jangbu-connect
A setup guide for connecting Korean tax, bank, card, and social-insurance data through CODEF, an external API service. It explains how users obtain their own CODEF credentials and store them locally.