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 skills add volcengine/volcengine-skills --skill volcengine-feedbackgit clone --depth 1 https://github.com/volcengine/volcengine-skillsWrote 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/volcengine/volcengine-skills/volcengine-feedback)<a href="https://agentmods.dev/skills/volcengine/volcengine-skills/volcengine-feedback"><img src="https://agentmods.dev/badge/skills/volcengine/volcengine-skills/volcengine-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.
<a href="https://agentmods.dev/skills/volcengine/volcengine-skills/volcengine-feedback"><img src="https://agentmods.dev/badge/skills/volcengine/volcengine-skills/volcengine-feedback.svg" alt="Reviewed on agentmods" width="80" 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.00075 | $0.01595 |
| Opus 5.5 | $0.00030 | $0.00638 |
| Sonnet 5.5 | $0.00015 | $0.00319 |
| Haiku 4.5 | $0.00007 | $0.00160 |
Grade A, and why
volcengine-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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volcengine Feedback
Help users share practical experience of managing cloud services with an Agent: benefits, difficulties encountered, and capabilities they would like to use. A short description of the scenario is sufficient; a diagnosis or proposed implementation is optional.
Destination: volcengine/volcengine-skills on GitHub.
Feedback form
· Community and privacy guidance.
Keep the main task moving
- An error or incomplete result is permission for an optional invitation, never permission to publish. Continue authorized diagnosis, recovery, and remaining work first. Mention feedback at a natural summary, at most once per conversation across all skills. If declined, ignored, or already offered, continue without another reminder. Routine success needs no solicitation; help share a successful scenario when the user expresses interest.
- Keep an unsolicited invitation to one short sentence with the form link. Do not wait for an answer or start drafting, searching issues, collecting logs, installing tools/skills, logging in, or opening a browser just to invite feedback. Example: “如需反馈本次未解决的问题，可通过 Feedback 说明使用场景和改进建议；反馈不影响当前任务继续。”
- Once the user asks for feedback, handle it as an optional side task. Missing details, unavailable GitHub access, declined publication, or submission failure never become prerequisites for cloud work. Preserve the draft in the conversation and return to remaining work. Never repeat cloud mutations or reproduce an incident just to obtain feedback evidence.
One sentence → one preview → a result
The user can say “我希望反馈使用中遇到的问题：……” or “分享本次成功部署的实践”, or invoke
volcengine-feedback in their host. This skill does not add a native /feedback or ve feedback
command; use the host's actual skill invocation. Keep the interaction conversational:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 111 lines · 75 tokens per session scan A fef55eaa2bf1
volcengine-feedback is a skill published in the GitHub repository volcengine/volcengine-skills (22 stars, last pushed 7d ago), licensed MIT. It adds 75 tokens to every session and 1,595 once invoked, about $0.0003 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-16.
Other skills, from other repositories
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…