feedback

feedback is a skill for Claude Code from basher83/lunar-claude. It costs 126 tokens per session (1,048 once invoked), scanned A, original, MIT.

A workflow that files GitHub issues to report confusion, failures, ideas, or new wording that could improve the tools. A GitHub issue is a tracked discussion about a repository.

In plain words
What is it for?
It is for reporting bugs, usability problems, improvement ideas, observations, and unfamiliar ways users describe requests.
Why use it?
It gives maintainers a record of problems and suggestions without requiring the user to write or organise an issue manually.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the blake-os plugin — 4 skills shipped together

Good fit It is for reporting bugs, usability problems, improvement ideas, observations, and unfamiliar ways users describe requests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/basher83/lunar-claude/feedback
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.

Any agent
npx skills add basher83/lunar-claude --skill feedback
Clone the repo
git clone --depth 1 https://github.com/basher83/lunar-claude

Made for: Claude Code.

Or install blake-os, the plugin that ships this one along with the rest of its 4 skills.

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 feedback

README.md
[![agentmods](https://agentmods.dev/badge/skills/basher83/lunar-claude/feedback/github.svg)](https://agentmods.dev/skills/basher83/lunar-claude/feedback)
Your own site
<a href="https://agentmods.dev/skills/basher83/lunar-claude/feedback"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/feedback/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.

agentmods 80×15 button for feedback

Your own site · 80×15
<a href="https://agentmods.dev/skills/basher83/lunar-claude/feedback"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,048 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00126 $0.01048
Opus 5.5 $0.00050 $0.00419
Sonnet 5.5 $0.00025 $0.00210
Haiku 4.5 $0.00013 $0.00105

Measured 2mo ago against content hash 53ce3bc42d47, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feedback 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 2mo 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.

plugins/personal/blake-os/skills/feedback/SKILL.md · 98 lines

How it starts

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

Feedback (issues router)

File a GitHub issue on this repo whenever something is worth getting back to Brent — friction, a bug, an idea, or a new way the user phrased a request. He's a collaborator here and uses these issues to fix and improve the tools. The user is Blake — not a developer; never make him deal with GitHub. File the issue; speak to him in plain language.

What to file, and how to label it

Match the signal to a type. The label is what lets Brent triage fast.

What gets noticed… Type Label
They're confused, lost, or "don't get" something Friction friction
Something errored, stopped, or didn't do what they expected Bug bug
"I wish it would…", an idea, a smoother way they wanted Improvement improvement
A phrase git-ops had to guess at to route (handed off to this skill) Vocabulary vocabulary
Anything else worth Brent seeing Observation observation

Capture their exact words, verbatim — especially for vocabulary. Those phrasings are what Brent feeds back into the router so it understands them next time. Never paraphrase the quote.

Before filing: don't duplicate

Search first. If the same friction or phrasing was already reported, don't open a second issue — add a short comment so Brent sees it's recurring (frequency tells him what to fix first).

gh issue list --search "<key words or the verbatim phrase>" --state all --limit 5
  • Close match exists → gh issue comment <number> --body "Heard again: \"<verbatim>\"" and stop.
  • No match → file a new one (next section).

Filing the issue

Confirm there's a repo context, make sure the label exists, then file:

gh repo view --json nameWithOwner -q .nameWithOwner   # fails loudly if no repo / no auth

# ensure the label exists (harmless if it already does)
gh label create <label> --color ededed 2>/dev/null || true

gh issue create \
  --title "[<type>] <short scannable summary>" \
  --label "<label>" \
  --body "$(cat <<'EOF'
**What they were doing:** <the task in plain terms>

**What they said (verbatim):** "<their exact words>"

**What happened:** <the outcome, or where it got stuck>

**Their reaction:** <confused / annoyed / fine — only if observed>
EOF
)"

Read the full file on GitHub · 98 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. 2mo ago First seen · 98 lines · 126 tokens per session scan A 53ce3bc42d47

Subscribe to this mod's changes

feedback is a skill published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 1,048 once invoked, about $0.0005 per session on Opus 5.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-09-03.

Related

feedback compared with skills from other repositories

feedback next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
feedbackbasher83/lunar-claudeSkill23todayMITA126Claude Code
merge-batchdiegosouzapw/OmniRouteSkill85k2d agoMITA46Claude Code
prowler-commitprowler-cloud/prowlerSkill15ktodayApache-2.0A44Claude Code, Codex
gh-auth-isolationgithub/gh-awSkill5.6ktodayMITA20Claude Code, Codex
comet-githubrpamis/cometSkill3.3ktodayMITA72Claude Code, Codex
github-skillzeenie-ai/OpenCompanySkill1.1ktodayMITA51Claude Code
re0-mergeLilMGenius/paperthinSkill1.4ktodayMITA51Claude Code, Codex