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 agentmods add commands/llamadrive/bengo-toolkit/report-issuegit clone --depth 1 https://github.com/llamadrive/bengo-toolkitWrote 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/llamadrive/bengo-toolkit/report-issue)<a href="https://agentmods.dev/commands/llamadrive/bengo-toolkit/report-issue"><img src="https://agentmods.dev/badge/commands/llamadrive/bengo-toolkit/report-issue.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00456 |
| Opus 5 | $0.00013 | $0.00228 |
| Sonnet 5 | $0.00005 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
report-issue 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.
What it actually says
bengo-toolkit に対する不具合の報告・機能の要望・感想を、GitHub アカウントなしで送るための slash command。
$ARGUMENTS の指定方法:
- 引数なし: 対話形式で種別と本文を聞く
--type bug/--type feature/--type otherを付けて起動すれば、その種別から開始する
動作の流れ
- 利用者から種別（不具合 / 機能要望 / その他）と本文を聞き取る
- プラグイン版・OS・実行環境などの自動診断情報を付けて、Markdown 形式の下書きを
~/.claude-bengo/reports/feedback_<日時>.mdに書き出す - その下書きを OS 既定のテキストエディタで開く（macOS は TextEdit、Windows はメモ帳、Linux は xdg-open）
- llama-drive.com のフィードバックフォームを、ブラウザで開く（種別と診断情報は URL の query param で渡してフォーム側が自動入力する）
- 利用者はエディタの本文を選択コピーし、フォームに貼り付けて、内容を確認してから送信する
自動送信はしない。 プラグインがネットワーク越しに送信することはない。送信はあくまで利用者の手元で、ブラウザ経由で行う。
Step 1
まず skills/report-issue/SKILL.md を Read ツールで読み込み、そこに記載された手順に従って実行する。
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.
- 3d ago First seen · 25 lines · 26 tokens per session scan A 37f72c9c93f7
report-issue is a command published in the GitHub repository llamadrive/bengo-toolkit (6 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 456 once invoked, about $0.0001 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.