feedback

A command for sending a problem or suggestion about the Workflow platform to its maintainers.

In plain words
What is it for?
Use it to submit platform feedback after reviewing the exact report, destination, attachments, and excluded information.
Why use it?
It provides a defined way to report errors, slow performance, poor experiences, or missing features while showing the proposed report before sending it.

Command

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 commands/go1c/workflow-plugin/feedback
Clone the repo
git clone --depth 1 https://github.com/Go1c/workflow-plugin
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 146 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.00032 $0.00146
Opus 5 $0.00016 $0.00073
Sonnet 5 $0.00006 $0.00029
Haiku 4.5 $0.00003 $0.00015

Measured yesterday against content hash 4396a8547c69, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

commands/feedback.md · 10 lines

What it actually says

调起 workflow-feedback 技能处理下面这条反馈。预设边界:只收集我主动提供的信息,不扫仓库、不读任何 Workflow 凭证;发送前把完整报告、目标 Host、附件清单与不发送清单逐字展示给我确认,内容一改就重新确认;拿到 202 回执后如实说明 sup_ 编号是待人工审核的收件,不是正式单。

反馈内容原文:

$ARGUMENTS

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. yesterday First seen · 10 lines · 32 tokens per session scan A 4396a8547c69

Subscribe to this mod's changes

feedback is a command published in the GitHub repository Go1c/workflow-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 146 once invoked, about $0.0002 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.