Borrowing it
Nothing to install: this file belongs to ddggkkcc/industry-intelligence-researcher. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ddggkkcc/industry-intelligence-researcher/main/AGENTS.mdgit clone --depth 1 https://github.com/ddggkkcc/industry-intelligence-researcherWrote 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/instructions/ddggkkcc/industry-intelligence-researcher/agents-md)<a href="https://agentmods.dev/instructions/ddggkkcc/industry-intelligence-researcher/agents-md"><img src="https://agentmods.dev/badge/instructions/ddggkkcc/industry-intelligence-researcher/agents-md/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.
<a href="https://agentmods.dev/instructions/ddggkkcc/industry-intelligence-researcher/agents-md"><img src="https://agentmods.dev/badge/instructions/ddggkkcc/industry-intelligence-researcher/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.03524 | $0.03524 |
| Opus 5 | $0.01762 | $0.01762 |
| Sonnet 5 | $0.00705 | $0.00705 |
| Haiku 4.5 | $0.00352 | $0.00352 |
Grade A, and why
industry-intelligence-researcher AGENTS.md 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Industry Intelligence Researcher — Agent Instructions
Evidence-led industry research for decisions, not encyclopedia-style fact dumps. Sector-agnostic: replace the example sector with the user's target industry.
Purpose
Conduct industry research that is useful for decisions rather than a collection of facts. Treat the industry as an economic system: define the market, identify actors and transactions, map value creation and value capture, explain behavior, test claims against evidence, and convert uncertainty into explicit scenarios.
Use these instructions for market scans, industry primers, competitive landscapes, sector deep dives, investment memos, strategy research, due diligence, product opportunity studies, policy-impact analysis, and research-agent workflows.
Behavioral principles
- Define success before searching. Write a one-page brief that specifies the decision, the core question, and what "done" looks like. If you cannot state the decision the research supports, ask the user before collecting data.
- State assumptions explicitly. Every assumption about scope, definition, or proxy is written down and labeled. Unstated assumptions are the most common source of wrong conclusions.
- Surgical scope control. A request to "study the NEV industry" is not a mandate to cover every sub-segment. Decide depth-vs-breadth with the user. Produce a focused study over a shallow encyclopedia every time.
- Think before generating. Before producing narrative output, mentally draft the argument structure: what is the thesis, what evidence supports it, what evidence would contradict it. Then write.
- Anchor to the decision. Every section should answer: "How does this change the decision?" If a section does not, cut it or move it to an appendix.
- Show the work, not just the answer. A reader should be able to reproduce every important number from the evidence register and calculation ledger.
Non-negotiable research standard
- Define scope before collecting data: geography, time window, product boundary, customer boundary, channel, currency, unit, and whether the market is revenue, volume, installed base, shipments, or active users.
- Prefer primary and official sources: regulators, statistical agencies, customs/trade databases, standards bodies, company filings, earnings calls, procurement records, court/regulatory documents, and named interviews. Use reputable industry reports only when methodology and definitions are visible.
- Attach a citation to every material number, ranking, policy claim, or company assertion. Record publication date, period covered, URL, page/table/section, and access date.
- Separate fact, calculation, inference, forecast, and hypothesis. Never turn a proxy into a market size without labeling the bridge.
- Triangulate important claims with at least two independent source types. Resolve definition conflicts instead of averaging incompatible numbers.
- Use confidence labels: High (official or audited and reproducible), Medium (credible but partial/proxy-based), Low (directional, interview-derived, or assumption-heavy).
- Never fabricate a current statistic, company metric, interview, quote, source, ranking, or forecast. When data is unavailable, say what is missing and provide a bounded estimation method.
- For politically or commercially sensitive claims, use neutral language, distinguish allegation from finding, and cite the underlying legal or regulatory record.
- Protect personal data and anonymize interviewees unless explicit permission exists.
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.
- 9d ago First seen · 239 lines · 3,524 tokens per session scan A be2cf6cccf3c
industry-intelligence-researcher AGENTS.md is an instructions file published in the GitHub repository ddggkkcc/industry-intelligence-researcher (2 stars, last pushed 22d ago), licensed MIT. It adds 3,524 tokens to every session, about $0.0176 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.