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.
git clone --depth 1 https://github.com/Kokai-Data/japan-business-dataWrote 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/commands/kokai-data/japan-business-data/legal-research)<a href="https://agentmods.dev/commands/kokai-data/japan-business-data/legal-research"><img src="https://agentmods.dev/badge/commands/kokai-data/japan-business-data/legal-research/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/commands/kokai-data/japan-business-data/legal-research"><img src="https://agentmods.dev/badge/commands/kokai-data/japan-business-data/legal-research.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.00030 | $0.00281 |
| Opus 5 | $0.00015 | $0.00140 |
| Sonnet 5 | $0.00006 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
legal-research 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
/legal-research
Search Japanese laws / cabinet orders / ministerial ordinances via e-Gov 法令検索 (デジタル庁) — or fetch full statute text + chapter / article structure for a specific law_id.
Usage:
/legal-research <keyword>— search by keyword (e.g.,/legal-research 中小企業,/legal-research 個人情報保護)/legal-research <law_id>— fetch full statute (e.g.,/legal-research 338AC0000000154)
Returns cited list of candidate laws OR verbatim 条文 + 4-layer authority strip + 弁護士 / 行政書士 / 司法書士 boundary disclaimer.
Calls search-egov-laws and / or get-egov-laws-data Skills (公式 e-Gov API v2, デジタル庁).
Boundary
Output is verbatim 公式 statute text — NOT legal advice / interpretation / 適用判定. 法令解釈 / 法的助言 / 訴訟戦略 requires certified Japanese 弁護士 / 行政書士 / 司法書士.
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 · 22 lines · 30 tokens per session scan A eab9eb3b808b
legal-research is a command published in the GitHub repository Kokai-Data/japan-business-data (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 281 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 commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
scope
Mandatory pre-flight scope check — verify an asset is in scope BEFORE any HTTP touch. Deterministic (deny-wins, default-deny) via engine/scope.py against the engagement's scope.md. Blocks out-of-scope testing. Usage: /scope [ ...].
p0-regulatory
Identifies regulatory requirements, DSGVO (GDPR) obligations, and legal knock-out criteria early on, before significant time is invested in the idea. A regulatory showstopper should be recognised as early as possible.
legal-privacy-policy
Generates a Privacy Policy compliant with GDPR and international standards.
customs-checklist
Direct invocation of the customs-checklist skill. Use for EU/RO import or export pre-clearance checklist, TARIC duty lookup, VAT estimation, and regulated-goods documentation flags.
mca
Run a 10-point MCA company check via the MCA portal.