environment-selection

environment-selection is a command for coding agents from oghie/skillsets. It costs 0 tokens per session (225 once invoked), scanned A, original, MIT.

A decision procedure for choosing how close software should run to the hardware, from custom hardware logic to distributed services. It compares timing, concurrency, memory, scheduling, and communication needs.

In plain words
What is it for?
Use it when selecting an implementation level for accelerators, hard or soft real-time systems, hosted services, edge devices, or geographically distributed software.
Why use it?
It prevents choosing a more complex implementation level than the requirements justify. It also records why other options were rejected and how the choice can be checked.

Command

Part of the skillsets plugin — 9 skills, 4 commands, 1 hook, 4 MCP servers shipped together

Install

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.

agentmods
npx agentmods add commands/oghie/skillsets/environment-selection
Clone the repo
git clone --depth 1 https://github.com/oghie/skillsets

Or install skillsets, the plugin that ships this one along with the rest of its 9 skills, 4 commands, 1 hook, 4 MCP servers.

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 environment-selection

README.md
[![agentmods](https://agentmods.dev/badge/commands/oghie/skillsets/environment-selection.svg)](https://agentmods.dev/commands/oghie/skillsets/environment-selection)
Your own site
<a href="https://agentmods.dev/commands/oghie/skillsets/environment-selection"><img src="https://agentmods.dev/badge/commands/oghie/skillsets/environment-selection.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 225 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00225
Opus 5 $0.00000 $0.00112
Sonnet 5 $0.00000 $0.00045
Haiku 4.5 $0.00000 $0.00022

Measured 3d ago against content hash 8e25687534ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

environment-selection 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 3d 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.

skills/realtime-systems-coding/commands/environment-selection.md · 26 lines

What it actually says

Environment Selection Command

Goal

Choose the lowest abstraction level that can satisfy the timing, concurrency, and operational constraints without unnecessary complexity.

Procedure

  1. State the timing goal and correctness property.
  2. Start from the highest maintainable level and move lower only when evidence demands it.
  3. Compare candidate levels using references/development-environments/abstraction-level-map.md.
  4. Identify the scheduling, clock, memory, and communication contract at each candidate level.
  5. Select the level with the clearest validation path.

Decision Hints

  • Choose Level -1 for custom cycle-level datapaths.
  • Choose Level 0 for accelerator/offload workloads where transfer overhead is justified.
  • Choose Level 1 for direct hardware or hard real-time control.
  • Choose Level 2 for isolated hosted systems with measured jitter tolerance.
  • Choose Level 3 for scalable soft real-time services and distributed workloads.
  • Choose Level 4 for locality, edge autonomy, and geographically distributed behavior.

Output

  • Selected level.
  • Rejected alternatives and why.
  • Required toolchain.
  • Verification commands and measurements.
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. 3d ago First seen · 26 lines · 0 tokens per session scan A 8e25687534ae

Subscribe to this mod's changes

environment-selection is a command published in the GitHub repository oghie/skillsets (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 225 tokens. 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.