wise-feedback

wise-feedback is a skill for Claude Code, Codex from e1024kb/wise-claude. It costs 192 tokens per session (3,621 once invoked), scanned A, original, MIT.

A feedback-reporting command for opening a GitHub issue about a wise skill or workflow. GitHub issues are tracked reports for bugs, suggestions, and other project feedback.

In plain words
What is it for?
Use it to report a problem, suggestion, or unexpected result from a wise skill or workflow.
Why use it?
It removes the need to collect environment details and manually format and submit a report. It keeps the report focused on the add-on rather than the user's project.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the wise plugin — 32 skills, 22 agents, 1 hook 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/e1024kb/wise-claude/wise-feedback
Any agent
npx skills add e1024kb/wise-claude --skill wise-feedback
Clone the repo
git clone --depth 1 https://github.com/e1024kb/wise-claude

Made for: Claude Code, Codex.

Or install wise, the plugin that ships this one along with the rest of its 32 skills, 22 agents, 1 hook.

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 wise-feedback

README.md
[![agentmods](https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-feedback.svg)](https://agentmods.dev/skills/e1024kb/wise-claude/wise-feedback)
Your own site
<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-feedback"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-feedback.svg" alt="Measured on agentmods" height="20"></a>
Per session 192 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,621 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.00192 $0.03621
Opus 5 $0.00096 $0.01810
Sonnet 5 $0.00038 $0.00724
Haiku 4.5 $0.00019 $0.00362

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

Security

Grade A, and why

wise-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 5d 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/wise/skills/wise-feedback/SKILL.md · 364 lines

How it starts

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

/wise-feedback — file a feedback issue against the marketplace

Why this skill exists

The wise plugin ships dozens of skills and workflows that users exercise many times a day. When one of them misbehaves — a workflow gets stuck, a skill returns a surprising result, a prompt is thin — the friction of "switch to browser, open github.com/e1024kb/wise-claude, click New Issue, fill three sections, remember to assign and label" is enough to swallow most of the feedback silently.

This skill closes the gap. A single /wise-feedback (optionally with a short free-form note) captures the environment, drafts the issue body, previews it, and creates the issue via gh issue create — already assigned to @e1024kb and tagged feedback.

Design principle — feedback is about the plugin, not the project

The single most important framing rule for this skill: the issue subject is the wise plugin, not the user's project. The user is reporting that a /wise-* skill or workflow needs to be improved or fixed; what they happened to be doing in their own codebase when the problem surfaced is incidental.

In practice that means:

  • The prompt and the session signal the skill draws from should describe the misbehaving wise component (which skill, which step, what it did wrong, what was expected), not the user's task at the time.
  • The Environment section keeps one project breadcrumb — the public git remote URL of the cwd, rendered as org/repo — so the triager knows which downstream repo surfaced the issue. It does NOT carry the branch, the short SHA, the file paths, the cwd, or anything else that describes in-flight work.
  • When the live transcript contains project-specific detail (filenames, branch names, ticket keys, paths), translate it into abstract symptoms before it reaches the issue body — e.g. "the skill aborted mid-edit on a TypeScript file" instead of "the skill aborted while editing src/components/Foo/Foo.tsx:42".

Read the full file on GitHub · 364 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. 5d ago First seen · 364 lines · 192 tokens per session scan A e75b6acfbe8d

Subscribe to this mod's changes

wise-feedback is a skill published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed yesterday), licensed MIT. It adds 192 tokens to every session and 3,621 once invoked, about $0.0010 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

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

google-ads-audit

Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…

nowork-studio/notfair-plugin · 114 tokens

review

5-pass structured code review — correctness, security, performance, readability, consistency.

SethGammon/Citadel · 17 tokens

ops-pocket

OPS on-demand: This skill should be used when the user asks to "pocket memos", "voice memo pipeline"…

Lifecycle-Innovations-Limited/claude-ops · 29 tokens

alive:system-upgrade

Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.

alivecontext/alive · 57 tokens

extract-resume

Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.

suxrobGM/jobpilot · 32 tokens