report-issue

report-issue is a skill for Claude Code, Codex from llamadrive/bengo-toolkit. It costs 97 tokens per session (1,924 once invoked), scanned A, original, MIT.

A feedback-reporting workflow that collects a bug report, feature request, or other feedback and opens a dedicated web form. It saves the draft locally for review.

In plain words
What is it for?
It is for preparing reports with a subject and description, opening the feedback form, and letting the user submit the reviewed text manually.
Why use it?
It gives people without GitHub accounts a way to report issues while ensuring nothing is submitted automatically.

Skill for Claude CodeCodex

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/report-issue
Any agent
npx skills add llamadrive/bengo-toolkit --skill report-issue
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 report-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/llamadrive/bengo-toolkit/report-issue.svg)](https://agentmods.dev/skills/llamadrive/bengo-toolkit/report-issue)
Your own site
<a href="https://agentmods.dev/skills/llamadrive/bengo-toolkit/report-issue"><img src="https://agentmods.dev/badge/skills/llamadrive/bengo-toolkit/report-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,924 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.00097 $0.01924
Opus 5 $0.00048 $0.00962
Sonnet 5 $0.00019 $0.00385
Haiku 4.5 $0.00010 $0.00192

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

Security

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 4d 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/report-issue/SKILL.md · 156 lines

How it starts

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

不具合報告・機能要望(report-issue)

弁護士は GitHub アカウントを持っていないことが多いため、専用フォーム(llama-drive.com/bengo-toolkit/feedback)に誘導する。プラグインは下書きをローカルファイルに書き出してテキストエディタで開き、ブラウザでフォームを開く。利用者は内容を確認してから手動で送信する(自動送信はしない)。

ワークフロー

Step 1: 種別の確認

$ARGUMENTS に --type bug / --type feature / --type other のいずれかがあればそれを使う。なければ以下を 1 度だけ尋ねる:

どの種別で送る?
  1. 不具合の報告(バグ)
  2. 機能の要望
  3. その他のフィードバック

番号で回答(未回答は 3):

回答を bug / feature / other のいずれかにマップする。

Step 2: 件名の確認(任意)

短く件名を教えてほしい(30 字程度。空のままでも OK):

未記入なら空のままで進める。

Step 3: 本文の聞き取り

種別に応じて以下を促す:

不具合(bug)の場合:

不具合の内容を教えてほしい。差し支えなければ以下を含めると対応がはやい:
  - どのコマンドで起きたか(例: /family-tree、/template-fill)
  - 再現手順(簡潔に箇条書き)
  - 期待していた動作
  - 実際の動作(エラーメッセージがあればそのまま貼ってよい)

事務所名・依頼者名・案件番号・PDF の本文引用などの機密情報は記載しないでほしい。
記載があった場合、こちらで一読する性質上、削除前提で扱う。

機能要望(feature)の場合:

どんな機能が欲しいか教えてほしい。差し支えなければ以下を含めると検討しやすい:
  - どんな場面で必要になったか
  - 現状はどう回避しているか
  - こんな出力・操作だと嬉しい、というイメージがあれば

事務所名・依頼者名・案件番号・PDF の本文引用などの機密情報は記載しないでほしい。

その他(other)の場合:

感想・要望など自由に書いてほしい。

事務所名・依頼者名・案件番号・PDF の本文引用などの機密情報は記載しないでほしい。

利用者の回答全文を本文として保持する。

Step 4: 本文を一時ファイルに書き出す

利用者の本文を Write ツールで一時ファイルに書き出す:

パス: /tmp/bengo-report-input-<unix epoch>.md
内容: 利用者の本文をそのまま

ファイル名の <unix epoch>date +%s の結果か、それに準ずるユニークな数値で構わない(既存ファイルと衝突しなければよい)。

Step 5: report.py emit を呼ぶ

python3 skills/_lib/report.py emit \
  --type <bug|feature|other> \
  --title "<Step 2 の件名 or 空>" \
  --body-file "<Step 4 で書いたパス>"

戻り値 JSON:

{
  "output_path": "/Users/.../.claude-bengo/reports/feedback_YYYYMMDD_HHMMSS.md",
  "form_url": "https://llama-drive.com/bengo-toolkit/feedback?type=...&version=...",
  "editor_opened": true,
  "browser_opened": true
}

このコマンドは以下を行う:

  • 本文と診断情報(プラグイン版・OS・surface)を統合した Markdown を ~/.claude-bengo/reports/feedback_*.md に保存
  • そのファイルを OS 既定のテキストエディタで開く
  • フォーム URL を既定のブラウザで開く

書き出し後、/tmp/bengo-report-input-*.md は削除して構わない。

Step 6: 利用者への案内

戻り値 JSON の値をもとに、以下のような案内を表示する:

下書きを書き出した:
  📝 {output_path}

  TextEdit(macOS)/ メモ帳(Windows)/ 既定のエディタで開いた。

送信フォームを開いた:
  🌐 {form_url}

エディタ側の本文を全選択コピー(macOS: ⌘A → ⌘C / Windows: Ctrl+A → Ctrl+C)
してから、ブラウザのフォーム本文欄に貼り付けて送信してほしい。

機密情報が紛れていないか、必ず読み直してから送信してほしい。

Read the full file on GitHub · 156 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. 4d ago First seen · 156 lines · 97 tokens per session scan A b7748bcf6307

Subscribe to this mod's changes

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