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 skills add cynco-labs/ai-accounting-skills --skill revenue-recognitiongit clone --depth 1 https://github.com/cynco-labs/ai-accounting-skillsWrote 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/revenue-recognition)<a href="https://agentmods.dev/skills/cynco-labs/ai-accounting-skills/revenue-recognition"><img src="https://agentmods.dev/badge/skills/cynco-labs/ai-accounting-skills/revenue-recognition/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/revenue-recognition"><img src="https://agentmods.dev/badge/skills/cynco-labs/ai-accounting-skills/revenue-recognition.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.00035 | $0.00293 |
| Opus 5 | $0.00017 | $0.00147 |
| Sonnet 5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
revenue-recognition 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
/revenue-recognition
Purpose
Thin alias into classify — revenue theme only.
Same doctrine: shared/classify-substance.md.
Same output folder: workpapers/analysis/revenue_recognition.md.
Steps
- Ensure
workpapers/transactions.jsonexists (run extract if not). - Set
classify_depth=standards_awarefor this theme. - Load
references/jurisdictions/malaysia/standards/revenue_recognition.md(or active jurisdiction pack). - Follow classify-transactions steps 1–3 focused on material credits / sales streams.
- Write
workpapers/analysis/revenue_recognition.mdfromreferences/schemas/analysis_pack.example.md. - Apply concluded COA codes; update
payee_map.json; re-run classify script for affected lines.
Done when: revenue pack on disk with sources, standard ref, conclusion → codes; open items listed.
Do not
- Invent a second pipeline
- Code all bank credits as sales without substance
- Skip structured asks when recognition date is ambiguous
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 · 30 lines · 35 tokens per session scan A 5a7789d663be
revenue-recognition is a skill published in the GitHub repository cynco-labs/ai-accounting-skills (3 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 293 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.