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/hachej/boring-ui/feedbacknpx skills add hachej/boring-ui --skill feedbackgit clone --depth 1 https://github.com/hachej/boring-uiWhat 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.00020 | $0.00353 |
| Opus 5 | $0.00010 | $0.00177 |
| Sonnet 5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
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 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
Feedback
Create the source GitHub issue and stop. Do not implement. Do not split into tickets.
Labels
Apply exactly one category when possible:
bugenhancement
Apply exactly one state:
needs-triage— clear enough for triageneeds-info— clarification is needed
Process
- Capture the report: observed behavior, expected behavior, route/panel/plugin, selected item, branch/SHA if available, environment/browser/app context, safe errors, optional screenshot.
- Redact before publishing: no secrets, cookies, auth headers, private data, unrelated transcripts, or host-local paths. Use safe attachment names/URLs only.
- If unclear enough to affect routing, ask only:
Grill now, defer, or skip?- grill now: clarify before final issue body.
- defer: create issue with
needs-info. - skip: create issue with best-known context and
needs-triage.
- Create the GitHub issue.
- Stop and return the issue URL plus next suggestion.
Issue Body
## Summary
## Observed
## Expected
## Context
- Route/panel:
- Package/plugin:
- Branch/SHA:
- Environment:
## Artifacts
## Redaction
## Acceptance
## Proof Ideas
- Exact command:
- Screenshot/demo:
- Manual steps:
- Waiver if proof is not possible:
## Open Questions
## Next
Suggested next step: `/triage #<issue>` or `/plan #<issue>`.
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 · 65 lines · 20 tokens per session scan A 11b930e08bff
feedback is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 353 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…