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 dev-toolings/superpowers-symfony --skill config-env-parametersgit clone --depth 1 https://github.com/dev-toolings/superpowers-symfonyWrote 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/dev-toolings/superpowers-symfony/config-env-parameters)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/config-env-parameters"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/config-env-parameters/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/dev-toolings/superpowers-symfony/config-env-parameters"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/config-env-parameters.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 11 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.
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.00022 | $0.00437 |
| Opus 5.5 | $0.00009 | $0.00175 |
| Sonnet 5.5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
config-env-parameters 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 17d 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
Config Env Parameters (Symfony)
Use when
- Adding or changing an environment variable, a parameter, or a secret.
- A value differs between environments (dev, test, prod).
- Casting or parsing env values (
int:,bool:,json:,csv:,file:). - Storing credentials in the Symfony secrets vault.
Default workflow
- Decide where the value lives:
.envdefault,.env.local, real environment, or the vault for secrets. - Declare it with a safe committed default, never a real credential.
- Inject it with
%env(...)%and the right processor, through a parameter or#[Autowire]. - Put environment-specific settings in
config/packages/<env>/orwhen@<env>blocks. - Fail fast in the service when a required value is empty.
Guardrails
- Never commit
.env.local,.env.*.localor the vault decryption key. - In production, set variables in the server or container environment, not in files.
- Env values are strings until processed: cast them, do not compare
"false"tofalse. - Remember the loading order:
.env,.env.local(skipped in test),.env.<env>,.env.<env>.local.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- Where each new value is defined, per environment.
- The injection point and the processor used.
- Secrets added to the vault, named but never printed.
References
reference.md
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.
- 17d ago Changed · +3 lines abd55bc04dd4
- 1mo ago Changed · +2 lines · -3 tokens per session e0397458471a
- 1mo ago First seen · 43 lines · 25 tokens per session scan A fe67d766a876
config-env-parameters is a skill published in the GitHub repository dev-toolings/superpowers-symfony (226 stars, last pushed 17d ago), licensed MIT. It adds 22 tokens to every session and 437 once invoked, about $0.0001 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.
Other skills, from other repositories
architecture-paradigm-cqrs-es
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
spine-design
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
warden-harden
Produce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".
cortex-integrate
Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
spine-api
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".
spine-perf
Find and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".