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 agentmods add skills/githubnext/gh-aw-workshop/micro-environment-simulatornpx skills add githubnext/gh-aw-workshop --skill micro-environment-simulatorgit clone --depth 1 https://github.com/githubnext/gh-aw-workshopWhat 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 | $0.00027 | $0.01119 |
| Opus 5 | $0.00014 | $0.00560 |
| Sonnet 5 | $0.00005 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
micro-environment-simulator 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
4 files 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.
- 2d ago First seen · 117 lines · 27 tokens per session scan A 870315dfeab9
micro-environment-simulator is a skill published in the GitHub repository githubnext/gh-aw-workshop (40 stars, last pushed 2d ago), with no licence file. It adds 27 tokens to every session and 1,119 once invoked, about $0.0001 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
review-pr
Review a GitHub or GitLab Pull/Merge Request and provide findings, and post structured review comments with issue explanation plus code fixes. Use this skill when asked to review a GitHub Pull Request or GitLab Merge Request.
scope-plan
First, before any planning work, tell the user: "scope-plan is deprecated — its replacements are write-plan (planning) and estimate-time (estimation). Continuing with scope-plan for now." Print this every time the skill runs, then proceed.
wbso-aanvraag
Analyseer een project op WBSO-waardigheid via Jira, code en documenten. Genereer de technische projectbeschrijving voor RVO, een S&O-uren schatting, en een lijst van Jira-epics/stories die gelabeld moeten worden voor urenregistratie. Gebruik deze skill wanneer de gebruiker vraagt om een WBSO-aanvraag, S&O-aanvraag, of…
write-plan
Create a technical implementation plan broken into small, executable, sized tasks. Use when user asks to create an implementation plan, break down a ticket, or scope work.
asvs-audit
Role: You are an Application Security Expert. Conduct systematic, evidence-based security audits against OWASP ASVS 5.0 Level 1 requirements using the bundled CSV as the canonical source.
estimate-size
Estimate software tickets and work items with a configurable relative-sizing workflow. Respect dedicated estimators and local project rules, and use the built-in defaults when no local rules are provided.