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 glincker/claude-code-marketplace --skill environment-managergit clone --depth 1 https://github.com/glincker/claude-code-marketplaceWrote 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/glincker/claude-code-marketplace/environment-manager)<a href="https://agentmods.dev/skills/glincker/claude-code-marketplace/environment-manager"><img src="https://agentmods.dev/badge/skills/glincker/claude-code-marketplace/environment-manager.svg" alt="Measured on agentmods" height="20"></a>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.00018 | $0.01099 |
| Opus 5 | $0.00009 | $0.00549 |
| Sonnet 5 | $0.00004 | $0.00220 |
| Haiku 4.5 | $0.00002 | $0.00110 |
Grade A, and why
environment-manager 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 7d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment Manager
Comprehensive environment configuration and secrets management agent. Handles .env files, environment variables, configuration validation, and secure secrets management across all environments.
Agent Expertise
- Environment variable management (.env files)
- Secrets management (AWS Secrets Manager, HashiCorp Vault, etc.)
- Configuration validation and type checking
- Environment-specific configs (dev, staging, prod)
- Docker environment configuration
- Kubernetes ConfigMaps and Secrets
- Environment migration and synchronization
- Security best practices for sensitive data
Key Capabilities
- Environment Setup: Create and configure .env files for all environments
- Secrets Management: Secure handling of API keys, tokens, and credentials
- Configuration Validation: Type checking and validation for env vars
- Environment Sync: Keep environments in sync across team members
- Documentation: Generate documentation for all environment variables
- Migration: Safely migrate configurations between environments
Workflow
When activated, this agent will:
- Analyze current environment configuration
- Identify missing or invalid environment variables
- Create .env.example templates for team sharing
- Set up secure secrets management
- Generate environment-specific configs
- Document all environment variables
Quick Commands
# Setup environment files
"Create .env files for development, staging, and production"
# Validate configuration
"Validate all environment variables in this project"
# Secrets management
"Set up secrets management with AWS Secrets Manager"
# Generate documentation
"Generate documentation for all environment variables"
# Environment sync
"Create .env.example from current .env"
# Migration
"Migrate environment config from .env to Kubernetes ConfigMap"
Features
Environment File Management
Creates structured .env files:
# .env.development
NODE_ENV=development
API_URL=http://localhost:3000
DATABASE_URL=postgresql://localhost:5432/myapp_dev
LOG_LEVEL=debug
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 191 lines · 18 tokens per session scan A e43567f02073
environment-manager is a skill published in the GitHub repository glincker/claude-code-marketplace (36 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,099 once invoked, about $0.0001 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-30.
Other skills, from other repositories
varlock
Secure environment variable management with Varlock. Use when handling secrets, API keys, credentials, or any sensitive configuration. Ensures secrets are never exposed in terminal, logs, or LLM context. Provides guidance around integrating varlock into a project, reading/editing .env.schema and other .env files…
varlock-agent-readiness
Use this skill to discover machine-readable metadata published by varlock.dev.
varlock-docs-search
Use this skill to discover and answer questions about varlock documentation with the remote MCP service or the llms.txt bundles.
implementing-secret-scanning-with-gitleaks
This skill covers implementing Gitleaks for detecting and preventing hardcoded secrets in git repositories. It addresses configuring pre-commit hooks, CI/CD pipeline integration, custom rule authoring for organization-specific secrets, baseline management for existing repositories, and remediation workflows for…
integrating-sast-into-github-actions-pipeline
This skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI/CD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and…
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…