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/jamestelfer/sandy/sandy-clinpx skills add jamestelfer/sandy --skill sandy-cligit clone --depth 1 https://github.com/jamestelfer/sandyWhat 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.00054 | $0.00179 |
| Opus 5 | $0.00027 | $0.00089 |
| Sonnet 5 | $0.00011 | $0.00036 |
| Haiku 4.5 | $0.00005 | $0.00018 |
Grade A, and why
sandy-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.
What it actually says
Sandy (CLI)
This plugin bootstraps the sandy command-line tool. Sandy's real instructions live in its
prime output, not here.
First action
Run in a shell:
sandy prime
Read its complete output before doing anything else. It documents the available sandy
subcommands, the IMDS credential flow, and the sandy resource sandy://skills/cli/resources/...
commands you need for script-authoring guidance.
Follow every resource link sandy prime gives you before writing or running a script.
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 · 24 lines · 54 tokens per session scan A ee82798a9eb3
sandy-cli is a skill published in the GitHub repository jamestelfer/sandy (7 stars, last pushed 28d ago), licensed Apache-2.0. It adds 54 tokens to every session and 179 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
ecs
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.
eks
AWS EKS Kubernetes management for clusters, node groups, and workloads. Use when creating clusters, configuring IRSA, managing node groups, deploying applications, or integrating with AWS services.
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.
ovh
OVHcloud infrastructure integration for managing instances, Kubernetes clusters, networks, and object storage via CLI and Terraform.
ak-cloud-deploy
Deploy an Agent Kernel project to AWS, Azure, or GCP using Terraform modules, or to any Kubernetes cluster (on-prem, baremetal, EKS) using the official Helm chart. Supports serverless and containerized modes for all three clouds. AWS supports execution modes (restsync, restasync, async, stream), queue-based scalable…
deploy
Deploy the current project to the cloud using Defang. Guides through CLI setup, authentication, compose file creation, stack selection, config management, and deployment.