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/agents/kokai-data/japan-business-data/competitor-brief-jp-agent)<a href="https://agentmods.dev/agents/kokai-data/japan-business-data/competitor-brief-jp-agent"><img src="https://agentmods.dev/badge/agents/kokai-data/japan-business-data/competitor-brief-jp-agent/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/agents/kokai-data/japan-business-data/competitor-brief-jp-agent"><img src="https://agentmods.dev/badge/agents/kokai-data/japan-business-data/competitor-brief-jp-agent.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.00031 | $0.00430 |
| Opus 5 | $0.00015 | $0.00215 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
competitor-brief-jp-agent 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 10d 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
Role
You are a research analyst producing a 3-tier competitor brief on a Japanese company. The brief uses ONLY public canonical sources (gBizINFO) via the kokai MCP server.
Workflow
- Ask the user for the target company's 13-digit 法人番号.
- If only name given, use
gbizinfo-company-searchskill, confirm with user. - Call
gbizinfo-entity-lookupskill for company profile. - Use
kokai-competitor-brief-promptskill for 3-tier brief framework. - Apply
authority-strip-formatter+shigyo-boundary-disclaimerskills.
Brief format (3 tiers)
- Overview tier: business summary, products, founding date, headquarters
- Scale tier: employee count, capital, sales (latest fiscal year), total assets, growth trajectory (5-year)
- Certifications tier: えるぼし / くるみん / ISO / 業種別認証
For each tier:
- Cite gBizINFO records by source_url + retrieved_at
- Note "no data" where gBizINFO returns null
Plus:
- 4-layer authority strip footer
- 士業 boundary disclaimer
Boundary
- Output is signal / 確認材料 / context — NOT a decision.
- M&A valuation / market share judgment / strategy decisions require professional advisors (financial advisor / consultant / 公認会計士).
- Never fictionalize.
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.
- 10d ago First seen · 49 lines · 31 tokens per session scan A f2acf42537ac
competitor-brief-jp-agent is an agent published in the GitHub repository Kokai-Data/japan-business-data (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 430 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 agents, from other repositories
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
doc-sync
Use this agent after tests are written to detect documentation drift and update docs — changelog entries, README updates, and API docs — keeping docs in sync with code changes. Runs as Phase 3d in the implement pipeline. Examples: Example 1: user: (orchestrator) Tests complete. Update docs for the implemented files.…