Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add kazukinagata/shinkoku/plugin install shinkokuWrote 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/kazukinagata/shinkoku/settlement)<a href="https://agentmods.dev/skills/kazukinagata/shinkoku/settlement"><img src="https://agentmods.dev/badge/skills/kazukinagata/shinkoku/settlement/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/kazukinagata/shinkoku/settlement"><img src="https://agentmods.dev/badge/skills/kazukinagata/shinkoku/settlement.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.00124 | $0.04252 |
| Opus 5 | $0.00062 | $0.02126 |
| Sonnet 5 | $0.00025 | $0.00850 |
| Haiku 4.5 | $0.00012 | $0.00425 |
Grade A, and why
settlement 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 11d 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
決算整理・決算書作成(Year-End Settlement)
会計年度末の決算整理仕訳を登録し、残高試算表・損益計算書・貸借対照表を確認するスキル。 journal スキルで日常仕訳の入力が完了していることを前提とする。
設定の読み込み(最初に実行)
shinkoku.config.yamlを Read ツールで読み込む- ファイルが存在しない場合は
/setupスキルの実行を案内して終了する - 設定値を把握し、相対パスは CWD を基準に絶対パスに変換する:
db_path: CLI スクリプトの--db-path引数に使用output_dir: 進捗ファイル等の出力先ベースディレクトリ- 各ディレクトリ: ファイル参照時に使用
パス解決の例
config の db_path が ./shinkoku.db、output_dir が ./output で CWD が /home/user/tax-2025/ の場合:
ledger.py trial-balance --db-path /home/user/tax-2025/shinkoku.db --input query.jsonshinkoku ledger bs --db-path /home/user/tax-2025/shinkoku.db --input query.json
進捗情報の読み込み
設定の読み込み後、引継書ファイルを読み込んで前ステップの結果を把握する。
.shinkoku/progress/progress-summary.mdを Read ツールで読み込む(存在する場合)- 以下の引継書を Read ツールで読み込む(存在する場合):
.shinkoku/progress/04-journal.md.shinkoku/progress/02-assess.md
- 読み込んだ情報を以降のステップで活用する(ユーザーへの再質問を避ける)
- ファイルが存在しない場合はスキップし、ユーザーに必要情報を直接確認する
基本方針
- journal スキルでの仕訳入力が完了しているか確認してから開始する
- 残高試算表で勘定残高を確認し、決算整理仕訳の必要性を判定する
- 減価償却は references/depreciation-rules.md のルールに基づいて計算する
- 決算整理仕訳も登録前に必ずユーザーに確認する
- 最終的に貸借対照表の貸借一致を検証する
前提条件の確認
決算処理を開始する前に以下を確認する:
- 日常仕訳が完了しているか: 未記帳の取引がないか確認を促す
- 会計年度: 対象年度を確認する(例: 2025年1月1日〜12月31日)
- 青色申告の種類: 65万円控除(複式簿記 + e-Tax/電子帳簿保存)、55万円控除(複式簿記 + 書面提出)、10万円控除(簡易帳簿)
- 前年確定申告の確認: 以下を assess の結果または前年の申告書から確認する
- 予定納税の有無と金額(所得税の前払い)
- 純損失の繰越控除の有無
- 前年の期末残高(当年の期首残高と一致するか)
- 前年の減価償却累計額(固定資産がある場合)
※ 前年データが未確認の場合は、先に assess スキルで確認するか、 ユーザーに前年の確定申告書を提示してもらう。
0-1. 期首残高の確認・設定
ledger.py ob-list --db-path DB --fiscal-year YEARで期首残高が設定済みか確認- 未設定の場合、ユーザーに以下を確認:
- 開業初年度か?(→ 期首残高なし、スキップ)
- 前年の確定申告書(青色申告決算書の貸借対照表)の期末列を提示してもらう
- 画像/PDFの場合は OCR で読み取り
- 前年の期末残高を
ob-set-batchで一括登録 - 登録後、
ob-listで内容を確認し、ユーザーに承認を得る
ステップ1: 残高試算表の確認
ledger.py trial-balance の呼び出し
shinkoku ledger trial-balance --db-path DB_PATH --input query.json
入力 JSON:
{
"fiscal_year": 2025
}
出力:
accounts: 各勘定科目の借方合計・貸方合計・残高total_debit: 借方合計total_credit: 貸方合計
What ships with it
2 files 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.
- 11d ago First seen · 393 lines · 124 tokens per session scan A 388680e25ea4
settlement is a skill published in the GitHub repository kazukinagata/shinkoku (359 stars, last pushed yesterday), licensed MIT. It adds 124 tokens to every session and 4,252 once invoked, about $0.0006 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
litestar-build
Auto-activate for uv build, hatch build, PyApp, PYAPP, wheel assets, GitHub release matrices, cargo-zigbuild, or python-build-standalone. Not for runtime deployment.
litestar-granian
Auto-activate for litestargranian, GranianPlugin, litestar run Granian options, runtime threads, HTTP/2, TLS, access logs, metrics, static mounts, or worker lifecycle. Not for non-Granian servers.
litestar-testing
Auto-activate for test.py, conftest.py, litestar.testing, TestClient, AsyncTestClient, createtestclient, createasynctestclient, anyio, Guard mocks, DI overrides, or handler tests. Not for generic pytest.
msgspec
Auto-activate for msgspec, Struct, Meta, msgspec.json, msgspec.msgpack, tagged unions, enchook, dechook, convert(), or Litestar DTO shapes. Not for Pydantic or ORM models — use their stack-specific skill.
litestar-autowire
Auto-activate for litestarautowire, AutowirePlugin, AutowireConfig, domainpackages, AutowireIntegration, AutowireLoader, or clearautowirecache. Not for manual Router composition — use explicit routes.
litestar-styleguide
Use when authoring Litestar skill content, Python/TypeScript examples, PEP 604, async I/O, Google docstrings, ruff/mypy/pyright, pytest, or CI rules. Not for focused Litestar APIs.