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 Agent-Engineer-Master/skill-engineer --skill assess-strategic-environmentgit clone --depth 1 https://github.com/Agent-Engineer-Master/skill-engineerWrote 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/agent-engineer-master/skill-engineer/assess-strategic-environment)<a href="https://agentmods.dev/skills/agent-engineer-master/skill-engineer/assess-strategic-environment"><img src="https://agentmods.dev/badge/skills/agent-engineer-master/skill-engineer/assess-strategic-environment.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.00226 | $0.02830 |
| Opus 5 | $0.00113 | $0.01415 |
| Sonnet 5 | $0.00045 | $0.00566 |
| Haiku 4.5 | $0.00023 | $0.00283 |
Grade C, and why
assess-strategic-environment scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Built with Agent Engineer Master — get your own production-ready skill: www.agentengineermaster.com/skill-engineer --> How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assess Strategic Environment
For a defined industry, diagnose the competitive environment type using BCG's Strategy Palette. Output: strategic-environment.md naming the environment in one causal sentence, evidencing the three diagnostic dimensions, flagging ambidexterity where present, and emitting a routing matrix that downstream sub-skills consume.
The discipline: Wrong environment diagnosis = wrong toolkit = useless output. A Classical analysis of an Adaptive industry produces a five-year plan that won't survive contact with reality. An Adaptive analysis of a Classical industry produces overcautious wait-and-see recommendations. This skill runs FIRST in the orchestrator chain.
Iron rules:
- Every dimension assessment carries V/C/A/I-tagged evidence — see
../_shared/provenance-tagging.md. - The classification named in one causal sentence ("Industrial robotics is Adaptive because trajectory is unforecastable beyond 18 months [C: ...], no single player can shape the standards landscape [C: ...], and demand is not in survival-mode [V: ...].").
- Three diagnostic dimensions independently assessed: predictability, malleability, harshness — none skipped, none collapsed.
- Routing matrix included — names Phase 1+2 sub-skills with heavy / light / skip designation per the diagnosed environment.
- 2026 terminology only — see
../_shared/2026-terminology.md. - Ambidexterity flagged when the industry genuinely spans two environments (different layers, geos, or customer segments).
Process
1. Intake
Confirm: industry slug, geographic scope (if relevant — the same industry can sit in different environments in different geos), focal layer (optional but recommended for multi-layer industries — see Five Forces focal-layer discipline). Read references/strategy-palette.md for the framework refresher and references/diagnostic-questions.md for the three-question discipline with per-environment anchors.
2. Assess predictability
Can the trajectory be reliably forecast over a 3-5 year horizon? Rate High / Medium / Low. Evidence anchors (see references/diagnostic-questions.md):
- Demand volatility (5yr coefficient of variation)
- Technology stability vs disruption cadence
- Regulatory cliffs / known mandates
- Number of viable strategic scenarios on a 5yr view
What ships with it
7 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.
- 7d ago First seen · 133 lines · 226 tokens per session scan C d314b096e1f1
assess-strategic-environment is a skill published in the GitHub repository Agent-Engineer-Master/skill-engineer (8 stars, last pushed 2mo ago), licensed MIT. It adds 226 tokens to every session and 2,830 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
get-history
Use when running on Claude Code and you need to examine past conversation, session logs, or raw chat history.
git-commit-per-topic
Use when the user asks to rewrite history so each commit introduces one working feature or bug fix, organize commits by topic, fold fixes into an earlier feature commit, or split a composite commit or class into independently buildable steps.
git-amend
Use when the user asks to amend the current Git commit.
git-merge-linear
Use when the user asks to merge a Git branch with linear history.
git-rebase
Use when the user asks to rebase a Git branch onto another base.
git-rewrite-history
Use when the user asks to rewrite Git history or use git-filter-repo.