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 skills add sapiom/sapiom-js --skill sapiom-sandbox-previewgit clone --depth 1 https://github.com/sapiom/sapiom-jsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sapiom/sapiom-js/sapiom-sandbox-preview)<a href="https://agentmods.dev/skills/sapiom/sapiom-js/sapiom-sandbox-preview"><img src="https://agentmods.dev/badge/skills/sapiom/sapiom-js/sapiom-sandbox-preview/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sapiom/sapiom-js/sapiom-sandbox-preview"><img src="https://agentmods.dev/badge/skills/sapiom/sapiom-js/sapiom-sandbox-preview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 31 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 17 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Prompt Injection · line 114 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 117 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 118 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 120 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 122 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
What 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.1 | $0.00149 | $0.02354 |
| Opus 5.5 | $0.00060 | $0.00942 |
| Sonnet 5.5 | $0.00030 | $0.00471 |
| Haiku 4.5 | $0.00015 | $0.00235 |
Grade A, and why
sapiom-sandbox-preview 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 2mo 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sandbox Previews & App Links
Two ways to put the web app in the current project on a live URL, both driven by the
sapiom-dev MCP (npx -y @sapiom/mcp; see the Get Started guide
if it isn't connected) and both reading the same sapiom.json resource:
| You want | Tool | The URL |
|---|---|---|
| To look at it now, iterate, throw it away | sapiom_dev_sandbox_preview |
Temporary — dies with the sandbox's ttl |
| A link that lasts, or that someone else opens | sapiom_dev_app_publish |
Durable — https://apps.sapiom.ai/{org}/{slug} |
This is not agent deployment. Sapiom agents deploy with sapiom_dev_agents_deploy;
both tools here host an ordinary app (Node server, static site, API, dashboard) from your
working directory.
Prerequisite
Run sapiom_authenticate once (browser login; caches a key in ~/.sapiom/credentials.json).
sapiom_dev_sandbox_preview and sapiom_dev_app_publish return a structured
not-authenticated error otherwise; configure and check only touch local files and work
signed-out. Check with sapiom_status.
The lifecycle
sapiom_dev_sandbox_configure— creates or updates a preview resource in the project'ssapiom.json. Fill the typed arguments instead of hand-writing JSON — the config is validated and written underresources.<name>(type: "sandbox"). Returns the stored config.sapiom_dev_sandbox_check(optional) — statically validates the resources without deploying. Returns{ ok, sandboxes, issues }; fix anyissuesbefore previewing.sapiom_dev_sandbox_preview— readssapiom.json, provisions the sandbox if needed, uploads the local code, builds, starts, and exposes a public URL. Returns{ name, url, status, logs }. Passnameonly when the project defines more than one resource.sapiom_dev_app_publish— when the link needs to outlive the sandbox. See below.
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.
- 2mo ago Changed · +20 lines a15edacb2793
- 2mo ago First seen · 148 lines · 149 tokens per session scan A 61e01d6e32c1
sapiom-sandbox-preview is a skill published in the GitHub repository sapiom/sapiom-js (22 stars, last pushed yesterday), licensed MIT. It adds 149 tokens to every session and 2,354 once invoked, about $0.0006 per session on Opus 5.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.
sapiom-sandbox-preview compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sapiom-sandbox-previewsapiom/sapiom-js | Skill | 22 | yesterday | MIT | A | 149 | Claude Code, Codex |
| gke-compute-classesgoogle/skills | Skill | 22k | yesterday | Apache-2.0 | A | 83 | Claude Code, Codex |
| gke-reliabilitygoogle/skills | Skill | 22k | yesterday | Apache-2.0 | A | 85 | Claude Code, Codex |
| gke-workload-securitygoogle/skills | Skill | 22k | yesterday | Apache-2.0 | A | 171 | Claude Code, Codex |
| cloud-architectJeffallan/claude-skills | Skill | 12k | 7d ago | MIT | A | 71 | Claude Code |
| nemo-automodel-launcher-configNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | A | 30 | Claude Code |
| azure-mgmt-botservice-dotnetmicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 78 | Claude Code |