Agentenv cli
CLI utilities for AI agents - fast Go replacements for common Python tools
npx -y skills add SebastianBoehler/agent-cli-utils --skill agentenv-cliAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Validate required environment variables with the local `agentenv` CLI. Use when an agent workflow needs a startup check, deployment validation, or a machine-readable report of missing or empty variables.
SKILL.md
1.4 KB, 279 tokens by cl100k_base, as published. Nobody here has run it
AgentEnv CLI
Use agentenv to check environment prerequisites before running a model, sync task, or automation step.
Invoke the Tool
Prefer the installed binary when it exists:
agentenv OPENAI_API_KEY HOME
If working inside this repository or the binary is not installed, run:
go run ./cmd/agentenv -- OPENAI_API_KEY HOME
Choose Flags
- Pass variable names as positional arguments for simple checks.
- Use
-file required-env.txtto load names from a file. - Use
-allow-emptyonly when blank values are acceptable. - Use
-show-valuesonly when exposing raw values is safe. - Use
-format jsonor-format yamlfor automation. - Use
-format textfor human review.
Apply Good Defaults
- Keep
-strict=truefor CI, startup checks, and agent preflight. - Avoid
-show-valuesunless the environment is trusted and the output will not be logged. - Prefer JSON output when a caller will branch on missing keys.
Examples
Validate a known set:
go run ./cmd/agentenv -- OPENAI_API_KEY AGENT_HOME MODEL_NAME
Load from file:
go run ./cmd/agentenv -- -file required-env.txt -format json
What ships with it: 1 file
207 B alongside SKILL.md
agents/
- openai.yaml207 B
Gives 0 of the 12 instructions most quality gates skills give in 279 tokens
Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07
- Read the output and check the exit codein 54 of 1195, across 14 files
- Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
- Identify the verification command proving the claimin 51 of 1195, across 12 files
- Run the full verification commandin 50 of 1195, across 11 files
- Verify output confirms the claimin 49 of 1195, across 12 files
- Check version control diff after agent delegationin 46 of 1195, across 6 files
- State claim with evidencein 44 of 1195, across 4 files
- Run the test suitein 33 of 1195, across 26 files
- Keep state in memory by defaultin 27 of 1195, across 6 files
- Make prototype runnable with one commandin 26 of 1195, across 5 files
- Produce a verification reportin 25 of 1195, across 14 files
- Detect the package manager from lockfilesin 24 of 1195, across 5 files
Said here and by no other author read
- check environment prerequisites before running a workflow
- use the installed binary when it exists
- pass variable names as positional arguments for simple checks
- use the file flag to load names from a file
- use the allow-empty flag only when blank values are acceptable
- use the show-values flag only when exposing values is safe
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.