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 skills/scaleway/scaleway-cli/nightly-test-debuggernpx skills add scaleway/scaleway-cli --skill nightly-test-debuggergit 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.00072 | $0.00728 |
| Opus 5 | $0.00036 | $0.00364 |
| Sonnet 5 | $0.00014 | $0.00146 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
nightly-test-debugger 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 3d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nightly Test Debugger
This skill helps you systematically analyze and debug failing nightly acceptance tests in the Scaleway CLI repository.
Understanding Nightly Tests
The nightly test suite (.github/workflows/nightly.yml) runs acceptance tests for all products daily at 00:00 UTC. Each product is tested in isolation with:
CLI_UPDATE_CASSETTES: true- Records API interactionsCLI_UPDATE_GOLDENS: true- Updates expected output files- Real API calls against Scaleway infrastructure
Common failure modes:
- API changes - Upstream API changed, test expectations no longer match
- Cassette mismatches - Recorded HTTP interactions don't match current behavior
- Golden file drift - Output format changed
- Infrastructure issues - Resource provisioning failures, quotas, timeouts
- Race conditions - Async operations not completing in expected time
- Dependency changes - Go module updates breaking compatibility
Debugging Workflow
Step 1: Gather Context
When investigating a failing nightly test, first collect the ID of the most recent run using:
gh run list --workflow "Nightly Acceptance Tests" --limit 1
Step 2: Read the Failure Logs
Fetch the full logs from the GitHub Actions run:
gh run view <RUN_ID> --log | grep FAIL:
This will give you names of the failed tests.
Step 3: Locate the Test File
Test files live in:
internal/namespaces/<product>/v<version>/<test_file>.go
Common patterns:
custom_<feature>_test.go- Feature-specific tests<product>_test.go- General tests
Read the failing test function to understand:
- What the test is trying to do
- What
BeforeFuncsetup runs - What
Checkassertions are made - What
AfterFunccleanup runs
Step 4: Categorize the Failure
Timeout/Infrastructure Failure
Symptoms:
context deadline exceeded
timeout waiting for resource
Diagnosis:
- Check if the timeout value is reasonable
- Look for resource provisioning delays
- Check for quota issues in the nightly environment
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.
- 3d ago First seen · 100 lines · 72 tokens per session scan A 2caf17f0481c
nightly-test-debugger is a skill published in the GitHub repository scaleway/scaleway-cli (996 stars, last pushed 3d ago), licensed Apache-2.0. It adds 72 tokens to every session and 728 once invoked, about $0.0004 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-30.
Other skills, from other repositories
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
verify
Build, launch and drive wayfinder-maps to verify a change end-to-end (server + headless browser).
run-evals
Run the manzanas-eval scenario benchmark harness against a daemon and read its determinism report. Use when validating daemon changes end-to-end, measuring action latency, or checking reset determinism.
ui-visual-regression
Automates visual regression testing for DB Console UI changes. Compares screenshots and network requests between the current branch and its merge base using roachprod, playwright-cli, and ImageMagick. Use when the user wants to verify UI changes haven't introduced visual or behavioral regressions.
lease-and-drive-a-sim
Drive an iOS simulator through a manzanasd daemon - acquire a lease, boot, dispatch composite/batch actions, observe/waitforelement, screenshot, and release with reset. Use whenever a task needs to interact with a simulator on a host running manzanasd instead of raw ssh+simctl+AXe.
testing-the-mcp-server
Test the libtmux-go MCP server end to end — drive the real binary over raw JSON-RPC, run the exhaustive advertised-schema gate, and point installed agent CLIs (Claude, Codex, Cursor, Gemini, grok, agy, opencode) at a local build. Use when verifying the server beyond go test, checking a branch works in a real client…