analyze-industry

analyze-industry is a skill for Claude Code, Codex from Agent-Engineer-Master/skill-engineer. It costs 237 tokens per session (3,930 once invoked), scanned C, original, MIT.

An industry-analysis workflow that combines several established business strategy frameworks into a structured report about one industry.

In plain words
What is it for?
Use it to assess an industry, estimate its structure and opportunities, evaluate an entry or investment thesis, and record supporting evidence and signals.
Why use it?
It brings different ways of examining an industry into one review, so important questions about attractiveness, competition, growth and entry are less likely to be missed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions subagents.

Good fit Use it to assess an industry, estimate its structure and opportunities, evaluate an entry or investment thesis, and record supporting evidence and signals.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agent-engineer-master/skill-engineer/analyze-industry
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.

Any agent
npx skills add Agent-Engineer-Master/skill-engineer --skill analyze-industry
Clone the repo
git clone --depth 1 https://github.com/Agent-Engineer-Master/skill-engineer

Made for: Claude Code, Codex.

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 analyze-industry

README.md
[![agentmods](https://agentmods.dev/badge/skills/agent-engineer-master/skill-engineer/analyze-industry/github.svg)](https://agentmods.dev/skills/agent-engineer-master/skill-engineer/analyze-industry)
Your own site
<a href="https://agentmods.dev/skills/agent-engineer-master/skill-engineer/analyze-industry"><img src="https://agentmods.dev/badge/skills/agent-engineer-master/skill-engineer/analyze-industry/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for analyze-industry

Your own site · 80×15
<a href="https://agentmods.dev/skills/agent-engineer-master/skill-engineer/analyze-industry"><img src="https://agentmods.dev/badge/skills/agent-engineer-master/skill-engineer/analyze-industry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 237 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,930 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00237 $0.03930
Opus 5.5 $0.00095 $0.01572
Sonnet 5.5 $0.00047 $0.00786
Haiku 4.5 $0.00024 $0.00393

Measured 1mo ago against content hash 3fb5937e01c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

analyze-industry 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 1mo ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/bar_test.py, scripts/init_analysis.py, scripts/log_run.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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 -->
strategy/industry-analysis/analyze-industry/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyze Industry

For a single industry-structure question (attractiveness, entry, allocation, roll-up thesis), produce a thesis-grade industry brief synthesizing 4-8 MBB analytical lenses. Three-layer output: narrative synthesis rendered as an HTML report (industry-brief.html), structured filters (industry-brief.yaml), append-only catalysts (signals-log.md). Three approval gates. Fresh-context senior-analyst bar test.

The bar (per _shared/bar-test.md): a senior sub-sector analyst reading the brief should find ≥3 non-obvious observations and zero obvious-missing.

Iron rules:

  • Every external fact-claim carries a V/C/A/I tag — see ../_shared/provenance-tagging.md.
  • Synthesis structured Pyramid + SCQA — see ../_shared/pyramid-scqa.md.
  • 2026 terminology only — see ../_shared/2026-terminology.md.
  • Brief never ships without bar test pass — see ../_shared/bar-test.md.
  • The reader-facing brief ships as a single self-contained HTML report (industry-brief.html) rendered via the html-output skill — never markdown. Machine/audit artifacts (industry-brief.yaml, signals-log.md, bar-test.md, working/*.md) stay markdown/YAML — see ../_shared/output-conventions.md.
  • The HTML brief clears analysis-quality-review Pass 1 (structure) and Pass 2 (readability) before Gate 3 — see step 9.

Process

1. Intake

Ask: industry slug, scope question (e.g., "is industrial robotics attractive for a sponsor-backed roll-up?"), mode (Quick / Deep), optional docs folder (industry reports, expert interview notes, target company materials). Run python scripts/init_analysis.py --slug <industry-slug> --question "<scope-question>" --mode <quick|deep> to create the industry folder.

2. Gate 1 — Scope + market definition (STOP)

Read references/gate-prompts.md Gate 1 template. Present: 3 candidate market framings (broad/sharpened/surgical) using the four-test discipline (specificity, measurability, supply-side coherence, customer coherence) + the sub-skill battery proposed for the chosen mode. User confirms framing + sub-skill cut. python scripts/log_run.py --event gate-1-approved.

Read the full file on GitHub · 125 lines

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. 1mo ago First seen · 125 lines · 237 tokens per session scan C 3fb5937e01c7

Subscribe to this mod's changes

analyze-industry is a skill published in the GitHub repository Agent-Engineer-Master/skill-engineer (8 stars, last pushed 3mo ago), licensed MIT. It adds 237 tokens to every session and 3,930 once invoked, about $0.0009 per session on Opus 5.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.

Related

Other skills, from other repositories

openspec-verify-change

Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".

Fission-AI/OpenSpec · 51 tokens

openspec-new-change

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach. Also use when the user says "openspec new change" or "opsx new".

Fission-AI/OpenSpec · 58 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

memory-system

A guide to giving an AI agent persistent, user-specific memory across conversations. It covers what to remember, how to store it, how to update or compress it, and when to use memory instead of a shared knowledge base.

bojieli/ai-agent-book · 95 tokens

extract

Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.

semantica-agi/semantica · 59 tokens

writing

A writing guide for turning verified facts and calculations into finished text for a specific audience. It follows the requested language, structure, and length.

bojieli/ai-agent-book · 27 tokens