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 fpindej/netrock --skill add-env-vargit clone --depth 1 https://github.com/fpindej/netrockWrote 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/fpindej/netrock/add-env-var)<a href="https://agentmods.dev/skills/fpindej/netrock/add-env-var"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/add-env-var.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.00008 | $0.00358 |
| Opus 5 | $0.00004 | $0.00179 |
| Sonnet 5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
add-env-var 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.
What it actually says
Adds an environment variable (backend or frontend).
Backend-consumed variable
- Add to
appsettings.Development.jsonif it needs a dev-specific value (Aspire injects infrastructure connection strings automatically - only add behavioral config here) - If it maps to an Options class: use
Section:Keynaming in appsettings (e.g.,Authentication:Jwt:AccessTokenLifetime) - If it needs Aspire wiring for local dev: add via
.WithEnvironment()inMyProject.AppHost/Program.cs - If it needs an Options class: use
/add-options-class
Frontend-consumed variable
- Add to
src/frontend/.env.example(documentation with placeholder) - Add to
src/frontend/.env.test(valid test value for CI) - Add to
src/frontend/src/lib/config/server.ts(server-only) ori18n.ts(client-safe) - Never export server config from the barrel (
$lib/config/index.ts)
Frontend PUBLIC_* variable (SvelteKit $env/static/public)
- Steps 1-2 above
- Add
ARG+ENVtosrc/frontend/Dockerfile(beforepnpm run build) - Add
--build-argto.github/workflows/docker.yml - Import:
import { PUBLIC_VAR } from '$env/static/public';
For secrets or keys that differ per environment (like Turnstile site keys), prefer runtime configuration via
$env/dynamic/privatewith SSR layout data instead of build-timePUBLIC_*args.
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 · 30 lines · 8 tokens per session scan A 68abc8cf0e0b
add-env-var is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 358 once invoked, about $0.0000 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
api-design
Guidelines for RESTful API design, endpoint naming conventions, and standardizing JSON responses.
python
Enforces FastAPI, Dependency Injection, and general Python coding standards based on the repository structure.
python-testing
Guidelines for Python testing using pytest and pytest-asyncio. Use when writing or debugging backend tests.
react
Guidelines for the React frontend, TanStack ecosystem, and React 19 standards. Use when modifying the UI.
react-testing
Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.
documentation
Standards for code documentation, docstrings, and maintaining README files.