verify

verify is a skill for Claude Code, Codex from llamadrive/bengo-toolkit. It costs 52 tokens per session (2,144 once invoked), scanned A, original, MIT.

A verification workflow for the bengo-toolkit, a legal-work plugin, that checks its connections, sample files, and security dependencies.

In plain words
What is it for?
It is for running connection checks against spreadsheet, document, and agent-file tools, confirming sample files exist, and checking that pinned software dependencies have not changed.
Why use it?
It helps determine whether the plugin is installed and responding correctly before using it with legal documents.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the bengo-toolkit plugin — 15 skills, 25 commands, 3 MCP servers shipped together

Install

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.

agentmods
npx agentmods add skills/llamadrive/bengo-toolkit/verify
Any agent
npx skills add llamadrive/bengo-toolkit --skill verify
Clone the repo
git clone --depth 1 https://github.com/llamadrive/bengo-toolkit

Made for: Claude Code, Codex.

Or install bengo-toolkit, the plugin that ships this one along with the rest of its 15 skills, 25 commands, 3 MCP servers.

Wrote 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.

agentmods badge for verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/llamadrive/bengo-toolkit/verify.svg)](https://agentmods.dev/skills/llamadrive/bengo-toolkit/verify)
Your own site
<a href="https://agentmods.dev/skills/llamadrive/bengo-toolkit/verify"><img src="https://agentmods.dev/badge/skills/llamadrive/bengo-toolkit/verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,144 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00052 $0.02144
Opus 5 $0.00026 $0.01072
Sonnet 5 $0.00010 $0.00429
Haiku 4.5 $0.00005 $0.00214

Measured 3d ago against content hash e0a6be0d2113, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

verify 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 3d 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.

skills/verify/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

動作確認(verify)

bengo-toolkit プラグインの各機能が正常に動作するか確認する。

モード

$ARGUMENTS の値に応じて3つのモードで動作する:

モード1: 接続テスト(引数なし)

MCP サーバの疎通と fixtures の存在を確認する。

手順: 0. プラグイン更新チェックはスキップする。Claude Code の /plugin install bengo-toolkit@llamadrive が marketplace.json の最新 version を見て更新する。 0.5. MCP サプライチェーン整合性(v3.3.0〜 必須): python3 scripts/verify_mcp_integrity.py を実行し、.mcp.json の各依存パッケージの npm integrity が scripts/mcp_pinned.json と一致することを確認する。不一致の場合は他の検証に進まず、即座にサプライチェーン改ざんの可能性を報告する(機密文書処理を継続してはならない)。

  1. mcp__xlsx-editor__get_workbook_info を任意の fixtures XLSX に対して呼び出し、応答を確認する。
  2. mcp__docx-editor__get_document_info を任意の fixtures DOCX に対して呼び出し、応答を確認する。
  3. mcp__agent-format__render_agent_file に同梱 fixture の絶対パス ${CLAUDE_PLUGIN_ROOT}/fixtures/agent-format/ping.agent を渡して、応答(Loaded ping.agent (0 sections). Rendering inline. 等)が返ることを確認する。この MCP は任意項目(family-tree / lawsuit-analysis / env の成果物は自己完結 HTML で生成するため、本 MCP は MCP Apps でのインライン描画にのみ使う)。未設定/未応答なら WARNING 扱いで先に進む。
    • 注: render_agent_inlinedata 引数)は使わない。 agent-format 0.1.9〜最新 0.2.3 で、data が型無し宣言のため MCP クライアントが文字列化して渡し、サーバ側の typeof data === "object" 判定に落ちて、どんな有効な .agent を渡しても常に missing or non-array sections を返す既知の upstream 不具合がある。実描画に使う render_agent_filepath 引数)はファイルを読んで JSON.parse するため正常に動作する。実スキル(family-tree / lawsuit-analysis / env)も render_agent_file を使っている。 3.5. 自己完結 HTML 描画エンジン(family-tree / lawsuit-analysis の成果物経路、必須): python3 skills/_lib/agent_html/build_html.py hostcli または inline を返し、skills/_lib/agent_html/dist/renderer_bundle.jsrenderer_styles.css が存在することを確認する。bash tests/agent_html.sh を実行すれば、極小の .agent から生成した HTML に connect-src 'none'(CSP)と描画エンジンが inline されること・外部リソースを一切参照しないことまで一括検証できる。
  4. Glob で fixtures/ 配下の各サブディレクトリにファイルが存在することを確認する。
  5. Glob で templates/_schema.yaml が存在することを確認する。
  6. Glob で skills/*/SKILL.md を検索し、見つかったスキルを列挙する。件数はハードコードしない — Glob の結果をそのまま使う。

出力:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  bengo-toolkit 動作確認レポート
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  [1] xlsx-editor MCP ............. OK
  [2] docx-editor MCP ............. OK
  [3] agent-format MCP ............ OK(任意・インライン描画用)
  [3b] 自己完結HTML描画エンジン ... OK
  [4] fixtures .................... OK ({N} dirs)
  [5] templates ................... OK
  [6] skills ...................... OK ({M} skills)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  結果: 全項目 OK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Read the full file on GitHub · 125 lines

Changes

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.

  1. 3d ago First seen · 125 lines · 52 tokens per session scan A e0a6be0d2113

Subscribe to this mod's changes

verify is a skill published in the GitHub repository llamadrive/bengo-toolkit (6 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 2,144 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens