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 commands/scaleway/scaleway-cli/configgit clone --depth 1 https://github.com/scaleway/scaleway-cliWhat 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.00000 | $0.01845 |
| Opus 5 | $0.00000 | $0.00923 |
| Sonnet 5 | $0.00000 | $0.00369 |
| Haiku 4.5 | $0.00000 | $0.00185 |
Grade A, and why
config 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 2d 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation for scw config
Config management engine is common across all Scaleway developer tools (CLI, terraform, SDK, ... ). It allows to handle Scaleway config through two ways: environment variables and/or config file. Default path for configuration file is based on the following priority order:
- $SCW_CONFIG_PATH
- $XDG_CONFIG_HOME/scw/config.yaml
- $HOME/.config/scw/config.yaml
- $USERPROFILE/.config/scw/config.yaml
In this CLI, environment variables have priority over the configuration file.
The following environment variables are supported:
| Environment Variable | Description |
|---|---|
| SCW_ACCESS_KEY | The access key of a token (create a token at https://console.scaleway.com/iam/api-keys) |
| SCW_SECRET_KEY | The secret key of a token (create a token at https://console.scaleway.com/iam/api-keys) |
| SCW_DEFAULT_ORGANIZATION_ID | The default organization ID (get your organization ID at https://console.scaleway.com/iam/api-keys) |
| SCW_DEFAULT_PROJECT_ID | The default project ID (get your project ID at https://console.scaleway.com/iam/api-keys) |
| SCW_DEFAULT_REGION | The default region |
| SCW_DEFAULT_ZONE | The default availability zone |
| SCW_API_URL | URL of the API |
| SCW_INSECURE | Set this to true to enable the insecure mode |
| SCW_PROFILE | Set the config profile to use |
Read more about the config management engine at https://github.com/scaleway/scaleway-sdk-go/tree/master/scw#scaleway-config
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.
- 2d ago First seen · 323 lines · 0 tokens per session scan A 4d57f071cdeb
config is a command published in the GitHub repository scaleway/scaleway-cli (996 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,845 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.
Other commands, from other repositories
canvas
Canvas LMS CLI - Interact with Canvas from the command line.
openui-integrate
Wire up the LLM backend — the core integration command.
canvas_account-features
Manage Canvas account feature flags and settings.
canvas_account-content-migrations_get
Command "canvas_account-content-migrations_get" from jjuanrivvera/canvas-cli, covering canvas account-content-migrations get, options, options inherited from parent commands and see also.
canvas_account-logins_update
Command "canvas_account-logins_update" from jjuanrivvera/canvas-cli, covering canvas account-logins update, options, options inherited from parent commands and see also.
plan
Show diff between YAML and current GitHub state. No mutations are made.