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 Kokai-Data/japan-business-data --skill search-procurement-portalgit 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/skills/kokai-data/japan-business-data/search-procurement-portal)<a href="https://agentmods.dev/skills/kokai-data/japan-business-data/search-procurement-portal"><img src="https://agentmods.dev/badge/skills/kokai-data/japan-business-data/search-procurement-portal/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/kokai-data/japan-business-data/search-procurement-portal"><img src="https://agentmods.dev/badge/skills/kokai-data/japan-business-data/search-procurement-portal.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.00136 | $0.01488 |
| Opus 5 | $0.00068 | $0.00744 |
| Sonnet 5 | $0.00027 | $0.00298 |
| Haiku 4.5 | $0.00014 | $0.00149 |
Grade A, and why
search-procurement-portal 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use this skill when:
- The user (sales / consultant / 行政書士 / 中小企業診断士) asks "what procurement notices has 〇〇 自治体 issued recently?"
- You need to discover bid opportunities by category (e.g., "システム開発", "建設", "物品調達") or by issuing organization (省庁 / 自治体).
- M&A target research requires understanding a company's potential government clients (which agencies publish RFPs in the target's industry).
- Subsidy-fit-jp follow-up: identify government procurement that complements a subsidy program.
- Pre-meeting research with a sales lead in B2G (business-to-government) space.
How to invoke
Call the kokai MCP server's search_procurement_portal tool:
{
"name": "search_procurement_portal",
"arguments": {
"query": "<free-text keyword (項目横断), e.g., システム開発>",
"project_name": "<公告名 partial match>",
"organization_name": "<発注機関 partial match, e.g., 中小企業庁 or 東京都>",
"lg_code": "<自治体コード, e.g., 130001 for 東京都>",
"category": "<業種分類, optional>",
"procedure_type": "<入札方式, optional: 一般競争 / 指名競争 / 随意契約>",
"count": 20
}
}
Required (one of): query / project_name / organization_name / lg_code. category and procedure_type are optional filters (cannot be used alone, public API constraint).
count defaults to 20, Kokai defensive cap = 100 (official max = 1000).
Output structure
For each procurement notice:
result_id(ResultId、internal ID)key(Key、source_urlfallback 用)project_name(公告名)organization_name(発注機関)cft_issue_date(公告日 = Call for Tender Issue Date)category(業種分類, e.g., システム開発 / 建設 / 物品調達)procedure_type(入札方式)source_url(公告 detail page URL, fallback:https://www.kkj.go.jp/api/?Key=<Key>)phase_scope:{ phase: 1, included: "...", deferred_to_phase_2: "..." }source_authority:"official"(公式 cite_required layer)attribution_text:"出典: 官公需情報ポータル (中小企業庁) https://www.kkj.go.jp"
Phase 1 vs Phase 2 promise (重要)
Phase 1 (this skill) — Call for Tender (CFT) discovery only:
- ✅ project names / 公告名
- ✅ issuing organizations / 発注機関 (中央省庁 + 自治体)
- ✅ industry categories / 業種分類
- ✅ bid procedure types / 入札方式
- ✅ CFT issue dates / 公告日
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 · 100 lines · 0 tokens per session scan A 87cd7dc0d5c1
search-procurement-portal is a skill published in the GitHub repository Kokai-Data/japan-business-data (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 136 tokens to every session and 1,488 once invoked, about $0.0007 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 skills, from other repositories
business-intelligence-expert
Build comprehensive business intelligence solutions including data warehouses, ETL pipelines, interactive dashboards, and analytical reporting systems. Use when the user mentions BI, data warehousing, star or snowflake schemas, OLAP cubes, ETL/ELT pipelines, dashboards, KPIs, or analytical reporting.
tableau-to-preset
Guided workflow for converting a Tableau workbook (.twb or .twbx) to a Preset dashboard via Superset MCP tools. Parses TWB XML, scopes conversion to the target dashboard's worksheets, maps chart types, carries worksheet filters across, calls generatechart per worksheet, and assembles with generatedashboard. Use only…
preset-api
Prepare direct Preset API access: auth, JWT exchange, base URLs, pagination, Rison parameters, response handling, and shared API setup. Use only for direct API workflows; Do not use for MCP-only work.
preset-cli
Drive Preset's sup CLI (PyPI package superset-sup) for shell, scripting, CI/CD, and agent-driven Preset workflows. Use only for CLI workflows; Do not use for MCP-only work or for direct HTTP/SDK code paths.
preset-admin
Manage Preset teams, workspaces, memberships, invites, role identifiers, seat checks, and audit logs through direct Management API calls. Use only for direct API workflows; Do not use for MCP-only work.
preset-dashboards
Inspect Preset workspace dashboards, charts, dashboard composition, screenshots, thumbnails, chart data, and chart/dashboard operation routing through direct Superset API calls. Use only for direct API workflows; Do not use for MCP-only work.