feedback

Two Scaleway CLI commands for sending feedback to the team: one for a bug report and one for a feature request.

In plain words
What is it for?
Use `scw feedback bug` to report a bug or `scw feedback feature` to request a feature.
Why use it?
It gives developers a direct, predefined way to report problems or suggest changes from the command line.

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/scaleway/scaleway-cli/feedback
Clone the repo
git clone --depth 1 https://github.com/scaleway/scaleway-cli
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 117 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.00000 $0.00117
Opus 5 $0.00000 $0.00059
Sonnet 5 $0.00000 $0.00023
Haiku 4.5 $0.00000 $0.00012

Measured yesterday against content hash cf33dbb010e5, 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.

docs/commands/feedback.md · 33 lines

What it actually says

Documentation for scw feedback

Send feedback to the Scaleway CLI Team!

Send a bug-report

Send a bug-report to the Scaleway CLI team.

Send a bug-report to the Scaleway CLI team.

Usage:

scw feedback bug

Send a feature request

Send a feature request to the Scaleway CLI team.

Send a feature request to the Scaleway CLI team.

Usage:

scw feedback feature
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 · 33 lines · 0 tokens per session scan A cf33dbb010e5

Subscribe to this mod's changes

feedback is a command published in the GitHub repository scaleway/scaleway-cli (996 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 117 tokens. 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.