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/anthropics/knowledge-work-plugins/journal-entry-prepnpx skills add anthropics/knowledge-work-plugins --skill journal-entry-prepgit clone --depth 1 https://github.com/anthropics/knowledge-work-pluginsWhat 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.00050 | $0.01612 |
| Opus 5 | $0.00025 | $0.00806 |
| Sonnet 5 | $0.00010 | $0.00322 |
| Haiku 4.5 | $0.00005 | $0.00161 |
Grade A, and why
journal-entry-prep 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- journal-entry-prep — 100% identical, 0 lines differ
- journal-entry-prep — 98% identical, 1 lines differ
- journal-entry-prep — 98% identical, 1 lines differ
- journal-entry-prep-th — 94% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journal Entry Preparation
Important: This skill assists with journal entry workflows but does not provide financial advice. All entries should be reviewed by qualified financial professionals before posting.
Best practices, standard entry types, documentation requirements, and review workflows for journal entry preparation.
Standard Accrual Types and Their Entries
Accounts Payable Accruals
Accrue for goods or services received but not yet invoiced at period end.
Typical entry:
- Debit: Expense account (or capitalize if asset-qualifying)
- Credit: Accrued liabilities
Sources for calculation:
- Open purchase orders with confirmed receipts
- Contracts with services rendered but unbilled
- Recurring vendor arrangements (utilities, subscriptions, professional services)
- Employee expense reports submitted but not yet processed
Key considerations:
- Reverse in the following period (auto-reversal recommended)
- Use consistent estimation methodology period over period
- Document basis for estimates (PO amount, contract terms, historical run-rate)
- Track actual vs accrual to refine future estimates
Fixed Asset Depreciation
Book periodic depreciation expense for tangible and intangible assets.
Typical entry:
- Debit: Depreciation/amortization expense (by department or cost center)
- Credit: Accumulated depreciation/amortization
Depreciation methods:
- Straight-line: (Cost - Salvage) / Useful life — most common for financial reporting
- Declining balance: Accelerated method applying fixed rate to net book value
- Units of production: Based on actual usage or output vs total expected
Key considerations:
- Run depreciation from the fixed asset register or schedule
- Verify new additions are set up with correct useful life and method
- Check for disposals or impairments requiring write-off
- Ensure consistency between book and tax depreciation tracking
Prepaid Expense Amortization
Amortize prepaid expenses over their benefit period.
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 · 187 lines · 50 tokens per session scan A 122715fb1824
journal-entry-prep is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,791 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 1,612 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.