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 agents/cloudshipai/station/environmentsgit clone --depth 1 https://github.com/cloudshipai/stationWhat 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.00000 | $0.02710 |
| Opus 5 | $0.00000 | $0.01355 |
| Sonnet 5 | $0.00000 | $0.00542 |
| Haiku 4.5 | $0.00000 | $0.00271 |
Grade A, and why
ENVIRONMENTS 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 yesterday.
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 — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment Management
Station's environment system provides secure isolation for agents and tools across development, staging, and production environments. Each environment maintains its own MCP server pool, agent definitions, and configuration variables.
Environment Structure
Directory Layout
~/.config/station/environments/
├── default/
│ ├── agents/ # Agent .prompt files
│ │ ├── File Analyzer.prompt
│ │ ├── Security Scanner.prompt
│ │ └── Code Reviewer.prompt
│ ├── template.json # MCP server configurations
│ └── variables.yml # Environment-specific variables
├── staging/
│ ├── agents/
│ ├── template.json
│ └── variables.yml
└── production/
├── agents/
├── template.json
└── variables.yml
File-Based Configuration
Template Configuration (template.json):
{
"name": "development-environment",
"description": "Development environment with filesystem and security tools",
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem@latest",
"{{ .PROJECT_ROOT }}"
]
},
"ship-security": {
"command": "ship",
"args": ["mcp", "security", "--stdio"]
},
"database": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-postgres@latest"
],
"env": {
"POSTGRES_URL": "{{ .DATABASE_URL }}"
}
}
}
}
Environment Variables (variables.yml):
PROJECT_ROOT: "/home/user/projects"
DATABASE_URL: "postgresql://user:pass@localhost:5432/dev_db"
AWS_REGION: "us-east-1"
SLACK_WEBHOOK_URL: "https://hooks.slack.com/services/..."
LOG_LEVEL: "debug"
Environment Operations
Creating Environments
# Create new environment
stn env create production
# Create from template
stn env create staging --from-template development
# Create with custom configuration
stn env create testing --config ./custom-template.json
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.
- yesterday First seen · 473 lines · 0 tokens per session scan A dc2fe833bb1a
ENVIRONMENTS is an agent published in the GitHub repository cloudshipai/station (429 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,710 tokens. 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 agents, from other repositories
demo-site
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…
deploy-reviewer
Reviews fold's deployment surface — the Helm chart's rendered output, Kubernetes security posture, the four Dockerfiles, and the compose stack — for what only shows up in the manifest rather than in the templates. Use after changes under deploy/, before a chart release, or when auditing how fold actually runs in a…
release-verifier
Verifies a published fold release end to end from the outside — archives, checksums and their cosign signature, SBOMs, the four ghcr images, the OCI chart, and every sigstore attestation. Use after a tag's release workflow goes green, before announcing a release, or when someone asks whether a published artifact is…
mcp-spec-auditor
Audits fold against the normative MCP specification for the pinned revision — method shapes, required fields and headers, error-code allocation, caching and intermediary rules, and deprecations on the clock. Use when a change touches wire behavior, when a new protocol revision ships, or before bumping the conformance…
gateway-reviewer
Reviews fold changes against the gateway's architectural invariants — pipeline order, snapshot-based reload state, audit as the single exit door, the invisibility rule, the minted error-code registry, and proxy-path allocation discipline. Use proactively after any non-trivial change to gateway/, auth/, policy/, or…
integration-test-author
Writes and extends fold's integration tests using real MCP SDK peers behind the gateway. Use when a change needs test coverage — new gateway behavior, reload/discovery paths, policy or auth changes, or a repro for a reported bug.