discord-manager: Skill for Claude Code

.claude/skills/env-vars/SKILL.md

env-vars is a skill for Claude Code from seasonedcc/discord-manager. It costs 74 tokens per session (1,195 once invoked), scanned A, original, MIT.

A documented way to manage environment variables, which are configuration values supplied to an application at runtime. It separates variables needed by the framework from those used by the product.

In plain words
What is it for?
Add or rename variables, update example environment files, and connect validated settings to application components.
Why use it?
It keeps configuration validation clear and prevents framework code from depending on unrelated product settings.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is seasonedcc/discord-manager's own configuration. It tells Claude Code how to work on discord-manager itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything discord-manager configures →

Reuse

Borrowing it

Nothing to install: this file belongs to seasonedcc/discord-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/seasonedcc/discord-manager/main/.claude/skills/env-vars/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/seasonedcc/discord-manager

Made for: Claude Code.

Wrote 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.

agentmods badge for env-vars

README.md
[![agentmods](https://agentmods.dev/badge/skills/seasonedcc/discord-manager/env-vars/github.svg)](https://agentmods.dev/skills/seasonedcc/discord-manager/env-vars)
Your own site
<a href="https://agentmods.dev/skills/seasonedcc/discord-manager/env-vars"><img src="https://agentmods.dev/badge/skills/seasonedcc/discord-manager/env-vars/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.

agentmods 80×15 button for env-vars

Your own site · 80×15
<a href="https://agentmods.dev/skills/seasonedcc/discord-manager/env-vars"><img src="https://agentmods.dev/badge/skills/seasonedcc/discord-manager/env-vars.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,195 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.01195
Opus 5.5 $0.00030 $0.00478
Sonnet 5.5 $0.00015 $0.00239
Haiku 4.5 $0.00007 $0.00120

Measured 2mo ago against content hash a14ebf88ac70, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

env-vars 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.

.claude/skills/env-vars/SKILL.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Environment Variables

Everything here documents the repository as it is on main. If main disagrees with this file, main wins: follow it and flag the drift.

Configuration follows a two-tier pattern: a framework env holding only the vars framework code reads, and an app env holding every var (framework vars plus product vars).

Architecture

Framework env — app/framework/env.server.ts

Holds only what framework code needs — today, the database path. Framework files (db.server.ts, scheduler.server.ts) import env from ./env.server with a relative path. This is what keeps app/framework/ extractable: it validates only its own surface and never learns a product var exists.

App env — app/env.server.ts

Holds all vars: the framework vars again, plus the product vars (DISCORD_BOT_TOKEN, DISCORD_OWNER_USER_ID, DISCORD_GUILD_ID). It imports makeTypedEnv from make-typed-env and defines its own schema.

Product code — app/business/, app/mcp/, app/ingest/, app/db/, app/test/ — imports env from ~/env.server.

Why two independent singletons

Each env() parses process.env through its own makeTypedEnv instance. Caching is built into makeTypedEnv, so the () => getEnvironment(process.env) wrapper is enough. The two share no state, which is exactly the point: the framework validates what it needs, and the app validates everything.

Read configuration through env()

Application code never reads process.env directly. Every value arrives through env(), already validated and camelCased, so a missing or malformed variable fails loudly at startup instead of surfacing as undefined deep inside a query or a Discord call.

Adding a new env var

Product var (a new Discord setting, a new tuning knob)

  1. Add the Zod field to app/env.server.ts only
  2. Add the key, with an explanatory comment, to .env.example
  3. Add the value to the job-level env: block in .github/workflows/ci.yml
  4. Update the setup documentation if the owner has to obtain the value from somewhere
  5. Import env from ~/env.server in the consuming file

Read the full file on GitHub · 95 lines

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. 2mo ago First seen · 95 lines · 74 tokens per session scan A a14ebf88ac70

Subscribe to this mod's changes

env-vars is a skill published in the GitHub repository seasonedcc/discord-manager (3 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 1,195 once invoked, about $0.0003 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-31.

Related

env-vars compared with skills from other repositories

env-vars next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
env-varsseasonedcc/discord-managerSkill32d agoMITA74Claude Code
mem0-oss-to-platformmem0ai/mem0Skill68k2d agoApache-2.0A217Claude Code, Codex
azure-mgmt-botservice-dotnetmicrosoft/skillsSkill3.2kyesterdayMITA78Claude Code
fastapi-router-pymicrosoft/skillsSkill3.2kyesterdayMITA46Claude Code
dev-runtimelangwatch/langwatchSkill5.0kyesterdayApache-2.0A172Claude Code
api-designericrisco/rsc-harnessSkill5032d agoMITA105Claude Code, Codex
migrate-segw-to-raparc-mcp/arc-1Skill252yesterdayMITA106Claude Code