devsandbox-config

A guide for answering devsandbox configuration questions from its published documentation. Devsandbox is a sandbox for AI coding assistants, and TOML is a text format commonly used for configuration files.

In plain words
What is it for?
It helps identify valid keys, accepted values, file locations, and how settings merge for features such as isolation, proxying, HTTP filtering, credentials, and redaction.
Why use it?
It avoids unreliable answers based on memory, especially when an unknown configuration key is silently ignored.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add zekker6/devsandbox
agentmods
npx agentmods add plugins/zekker6/devsandbox/devsandbox-config
Clone the repo
git clone --depth 1 https://github.com/zekker6/devsandbox

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 1 skill cost 208 tokens a session between them.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

devsandbox-config 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.

.claude-plugin/devsandbox-config/.claude-plugin/plugin.json · 18 lines

What it actually says

{
  "name": "devsandbox-config",
  "description": "Answer devsandbox configuration questions from the published documentation instead of from memory",
  "author": {
    "name": "Zakhar Besarab"
  },
  "homepage": "https://zekker6.github.io/devsandbox/docs/",
  "repository": "https://github.com/zekker6/devsandbox",
  "license": "MIT",
  "keywords": [
    "devsandbox",
    "sandbox",
    "configuration",
    "toml",
    "isolation"
  ]
}
Contents

What it installs

The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 208 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Changes

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.

  1. 3d ago First seen · 18 lines scan A 9f3772dcb283

Subscribe to this mod's changes

devsandbox-config is a plugin published in the GitHub repository zekker6/devsandbox (10 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.