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 kazukinagata/shinkoku --skill e-bookkeeping-compliancegit clone --depth 1 https://github.com/kazukinagata/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/e-bookkeeping-compliance)<a href="https://agentmods.dev/skills/kazukinagata/shinkoku/e-bookkeeping-compliance"><img src="https://agentmods.dev/badge/skills/kazukinagata/shinkoku/e-bookkeeping-compliance/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/e-bookkeeping-compliance"><img src="https://agentmods.dev/badge/skills/kazukinagata/shinkoku/e-bookkeeping-compliance.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.00091 | $0.02589 |
| Opus 5 | $0.00046 | $0.01295 |
| Sonnet 5 | $0.00018 | $0.00518 |
| Haiku 4.5 | $0.00009 | $0.00259 |
Grade A, and why
e-bookkeeping-compliance 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 13d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
優良な電子帳簿コンプライアンス診断
税務調査への備え、または優良な電子帳簿の要件充足状況を診断するスキル。 電子帳簿保存法施行規則第5条第5項(優良な電子帳簿の要件)に基づき、 shinkoku の帳簿データが要件を満たしているかを自動チェックする。
前提知識
- 電帳法の要件詳細: /tax-ebookkeeping-context を実行する
- システム概要書:
docs/system-overview.md
Step 0: 前提確認
ユーザーに以下を確認する:
- DB パス:
--db-pathに使用するデータベースファイルのパス - 対象年度:
--fiscal-yearに使用する会計年度 - 届出書の提出状況: 「国税関係帳簿の電磁的記録等による保存等に係る届出書」を所轄税務署に提出済みか
届出について: 優良な電子帳簿の保存を適用するには、あらかじめ届出書の提出が必要です。 令和9年分から適用する場合は、令和8年中に届出書を提出する必要があります。 届出書の様式は国税庁ウェブサイトからダウンロードできます。
Step 1: 自動診断 & サマリー出力
以下のコマンドを実行してシステムの適合状況を診断する。 結果はテーブル形式でユーザーに提示する。
チェック項目と実行コマンド
| # | 要件 | 条文 | チェック方法 |
|---|---|---|---|
| G1 | システム関係書類の備付け | 施行規則2条2項1号 | docs/system-overview.md ファイルの存在を確認 |
| G2 | 見読可能性の確保 | 施行規則2条2項2号 | shinkoku ledger trial-balance --db-path <db> --fiscal-year <year> を実行し、正常出力を確認 |
| G3 | ダウンロード対応 | 施行規則2条2項3号 | shinkoku ledger search --db-path <db> --input <params> --format csv を実行し、CSV出力を確認 |
| G4 | 訂正・削除履歴 | 施行規則5条5項1号イ | shinkoku ledger audit-log --db-path <db> を実行し、テーブルが機能することを確認 |
| G5 | 相互関連性の確保 | 施行規則5条5項1号ロ | shinkoku ledger general-ledger --db-path <db> --fiscal-year <year> --account-code <code> を実行し、仕訳帳⇔総勘定元帳の関連を確認 |
| G6 | 取引先検索 | 施行規則5条5項1号ハ | counterparty_contains パラメータで検索を実行 |
| G7 | 日付・金額の範囲指定検索 | 施行規則5条5項1号ハ | date_from/date_to/amount_min/amount_max パラメータで検索を実行 |
| G8 | 組合せ検索 | 施行規則5条5項1号ハ | 日付+取引先+金額を組み合わせた検索を実行 |
診断手順
- G1:
docs/system-overview.mdの存在を確認する - G2: 残高試算表を生成する
shinkoku ledger trial-balance --db-path <db> --fiscal-year <year> - G3: 仕訳をCSV形式で出力する
(params にはshinkoku ledger search --db-path <db> --input <params> --format csv{"fiscal_year": <year>, "limit": 5}を指定) - G4: 監査ログを取得する
shinkoku ledger audit-log --db-path <db> - G5: 任意の勘定科目で総勘定元帳を出力する(仕訳が存在する科目を使用)
shinkoku ledger general-ledger --db-path <db> --fiscal-year <year> --account-code <code> - G6-G8: 検索機能のテスト
# G6: 取引先検索 shinkoku ledger search --db-path <db> --input <params> # params: {"fiscal_year": <year>, "counterparty_contains": "<取引先名の一部>"} # G7: 範囲指定検索 # params: {"fiscal_year": <year>, "date_from": "<開始日>", "date_to": "<終了日>", "amount_min": 1, "amount_max": 1000000} # G8: 組合せ検索 # params: {"fiscal_year": <year>, "date_from": "...", "counterparty_contains": "...", "amount_min": 1}
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.
- 13d ago First seen · 199 lines · 91 tokens per session scan A 3610db821aab
e-bookkeeping-compliance is a skill published in the GitHub repository kazukinagata/shinkoku (359 stars, last pushed 3d ago), licensed MIT. It adds 91 tokens to every session and 2,589 once invoked, about $0.0005 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
bionic-safety-net
Unified survival infrastructure: health, finance, legal safety, circuit breakers, and structural protection against all ruin classes. The last line of defense.
internal-controls-and-audit
Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is…
capital-structure-and-covenants
Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to…
revenue-recognition
Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms…
tax
Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check…
802-regulations-dora
Use when reviewing, designing, or modifying Java enterprise systems that may support financial entities, critical ICT services, third-party ICT provider integrations, or operational resilience obligations under DORA. This should trigger for requests such as Review a Java platform for DORA ICT risk controls; Design…