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/edge-servicesgit 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.08228 |
| Opus 5 | $0.00000 | $0.04114 |
| Sonnet 5 | $0.00000 | $0.01646 |
| Haiku 4.5 | $0.00000 | $0.00823 |
Grade A, and why
edge-services 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 — 1,082 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation for scw edge-services
Edge Services API
Backend-stage management commands
Backend-stage management commands.
Create backend stage
Create a new backend stage. You must specify a type of backend (scaleway_s3, scaleway_lb, etc.) to configure the origin.
Usage:
scw edge-services backend-stage create [arg=value ...]
Arguments:
| Name | Description | Argument Specifications |
|---|---|---|
| scaleway-s3.bucket-name | Name of the Bucket | |
| scaleway-s3.bucket-region | Region of the Bucket | |
| scaleway-s3.is-website | Defines whether the bucket website feature is enabled | |
| scaleway-lb.lbs.{index}.id | ID of the Load Balancer | |
| scaleway-lb.lbs.{index}.zone | Zone of the Load Balancer | |
| scaleway-lb.lbs.{index}.frontend-id | ID of the frontend linked to the Load Balancer | |
| scaleway-lb.lbs.{index}.is-ssl | Defines whether the Load Balancer's frontend handles SSL connections | |
| scaleway-lb.lbs.{index}.domain-name | Fully Qualified Domain Name (in the format subdomain.example.com) to use in HTTP requests sent towards your Load Balancer | |
| scaleway-lb.lbs.{index}.has-websocket | Defines whether to forward websocket requests to the load balancer | |
| pipeline-id | Pipeline ID the Backend stage belongs to | Required |
| scaleway-serverless-container.region | ||
| scaleway-serverless-container.container-id | ||
| scaleway-serverless-function.region | ||
| scaleway-serverless-function.function-id |
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 · 1,082 lines · 0 tokens per session scan A 49101f2aca2d
edge-services 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 8,228 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
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deploy
Build, test, deploy with staged rollout.
d1-migration
Run D1 migration workflow — generate, inspect, apply.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
deploy
Build a container image, push it, and deploy the service to the Akka platform. This is the transition from local development to development on the AAO platform.
scan
Scan AWS account for cost optimization.