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/signadot/cli/signadot-clinpx skills add signadot/cli --skill signadot-cligit clone --depth 1 https://github.com/signadot/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.00056 | $0.03107 |
| Opus 5 | $0.00028 | $0.01554 |
| Sonnet 5 | $0.00011 | $0.00621 |
| Haiku 4.5 | $0.00006 | $0.00311 |
Grade A, and why
signadot-cli 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 — 456 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Signadot CLI
Help the user manage Signadot resources using the signadot CLI. If the user specifies a resource type ($ARGUMENTS), focus on that section. Otherwise, provide guidance based on what they're trying to accomplish.
Core Concepts
- Sandbox: An isolated environment comprising forked workloads, local workloads, or virtual workloads plus ephemeral resources. Each sandbox gets a unique routing key for request routing.
- Route Group: Dynamically groups sandboxes by label criteria and provides shared preview URLs. Useful for combining multiple sandboxes into a single test environment.
- Preview URL: An authenticated URL that routes traffic to a specific sandbox or route group by automatically injecting the routing key.
- Resource Plugin: A reusable template for provisioning ephemeral resources (databases, queues, etc.) within sandboxes.
- Templates: YAML files with
@{variable}directives, expanded at apply time with--set variable=value.
Configuration
The main configuration for the CLI is authentication (org and optionally api key) and configuration for signadot local.
The CLI reads $HOME/.signadot/config.yaml by default. Use --config to switch:
signadot --config ~/configs/staging.yaml sandbox list
See authentication below for authentication information and the signadot-local skill
for local configuration.
Authentication
# Interactive browser login
signadot auth login
# API key login
signadot auth login --with-api-key <key>
# Check status
signadot auth status
# Logout
signadot auth logout
For CI, use environment variables: SIGNADOT_ORG and SIGNADOT_API_KEY.
Sandbox Management (alias: sb)
Create or Update a Sandbox
Write a YAML spec file and apply it:
# my-sandbox.yaml
name: my-sandbox
spec:
cluster: my-cluster
description: Testing new feature
forks:
- forkOf:
kind: Deployment
namespace: example
name: my-app
customizations:
images:
- image: example.com/my-app:dev-abcdef
container: my-app
env:
- name: FEATURE_FLAG
container: my-app
operation: upsert
value: "true"
defaultRouteGroup:
endpoints:
- name: my-endpoint
target: http://my-app.example.svc:8080
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 · 456 lines · 56 tokens per session scan A 337d64d19dcf
signadot-cli is a skill published in the GitHub repository signadot/cli (8 stars, last pushed 13d ago), licensed Apache-2.0. It adds 56 tokens to every session and 3,107 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.