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 skills/basher83/lunar-claude/feedbacknpx skills add basher83/lunar-claude --skill feedbackgit clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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/basher83/lunar-claude/feedback)<a href="https://agentmods.dev/skills/basher83/lunar-claude/feedback"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/feedback.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.1 | $0.00126 | $0.01048 |
| Opus 5 | $0.00063 | $0.00524 |
| Sonnet 5 | $0.00025 | $0.00210 |
| Haiku 4.5 | $0.00013 | $0.00105 |
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 2d 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 — 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
)"
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.
- 2d ago First seen · 98 lines · 126 tokens per session scan A 53ce3bc42d47
feedback is a skill published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 1,048 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…