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 agentlas-ai/agentlas-desktop --skill market-research-reportsgit clone --depth 1 https://github.com/agentlas-ai/agentlas-desktopWrote 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/agentlas-ai/agentlas-desktop/market-research-reports)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/market-research-reports"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/market-research-reports/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/skills/agentlas-ai/agentlas-desktop/market-research-reports"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/market-research-reports.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.00053 | $0.02951 |
| Opus 5.5 | $0.00021 | $0.01180 |
| Sonnet 5.5 | $0.00011 | $0.00590 |
| Haiku 4.5 | $0.00005 | $0.00295 |
Grade A, and why
market-research-reports 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 1mo 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.
This is a copy
100% identical to market-research-reports — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Research Reports
Purpose
Create decision-focused market reports whose claims, calculations, assumptions, and uncertainties can be audited. Match depth and format to the question and evidence. There is no required length, chapter count, visual count, or output format.
Do not:
- imitate or imply affiliation with a consulting, analyst, or research brand;
- invent citations, quotes, market shares, or paid-market figures;
- present TAM/SAM/SOM or a forecast as one certain truth;
- treat a framework, chart, or fluent narrative as evidence;
- provide investment, legal, antitrust, tax, accounting, or regulatory advice.
Operating principles
- Define before sizing. Fix product, customer, geography, channel, period, measure, unit, denominator, currency/base year, and taxonomy.
- Map every claim. Every factual or quantitative claim has a claim ID and exact source IDs.
- Separate statement types. Distinguish facts, estimates, calculations, forecasts, opinions, and recommendations.
- Prefer primary evidence. Use official statistics, regulator records, filed company disclosures, and transparent original studies before secondary synthesis.
- Preserve uncertainty. Retain source conflicts, revisions, scenario ranges, sensitivity, and limitations.
- Keep methods reproducible. Use local structured inputs and deterministic calculations when practical.
- Collect lawfully and ethically. No deception, PII disclosure, access circumvention, confidential material, or trade-secret acquisition.
Workflow
1. Establish the research contract
Clarify:
- decision, audience, deadline, and materiality threshold;
- formal market definition and adjacent exclusions;
- buyer, payer, user, transaction, and value-chain level;
- geography and treatment of imports, exports, and channels;
- historical period, forecast period, and retrieval cutoff;
- revenue/expenditure, gross output/value added, units, capacity, users, or another measure;
- stock/flow, gross/net, taxes, and denominator;
- currency, base year, and nominal/real/current/constant basis;
- industry and product classification with version;
- permitted data sources, primary research, confidentiality, and output format.
What ships with it
25 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.
- assets/claims_ledger_template.csv 957 B
- assets/competitor_feature_matrix_template.csv 683 B
- assets/consistency_check_template.csv 432 B
- assets/forecast_sensitivity_template.json 1.7 KB
- assets/FORMATTING_GUIDE.md 4.8 KB
- assets/market_report_template.tex 9.8 KB
- assets/market_research.sty 6.2 KB
- assets/market_sizing_scenarios_template.json 3.1 KB
- assets/report_manifest_template.json 882 B
- assets/source_ledger_template.csv 1.3 KB
- references/data_analysis_patterns.md 9.6 KB
- references/evidence_model.md 6.0 KB
- references/methods_and_ethics.md 7.3 KB
- references/official_data_sources.md 9.7 KB
- references/report_structure_guide.md 8.4 KB
- references/sources.md 9.2 KB
- references/visual_generation_guide.md 5.1 KB
- scripts/_common.py 11 KB runs code
- scripts/audit_claim_citations.py 11 KB runs code
- scripts/calculate_market_sizing.py 13 KB runs code
- scripts/check_unit_consistency.py 6.8 KB runs code
- scripts/forecast_sensitivity.py 11 KB runs code
- scripts/generate_report_scaffold.py 14 KB runs code
- scripts/validate_competitor_matrix.py 7.6 KB runs code
- scripts/validate_evidence_ledger.py 9.0 KB runs code
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.
- 1mo ago First seen · 355 lines · 53 tokens per session scan A d0e4899ac905
market-research-reports is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 2,951 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to market-research-reports, differing in 23 lines, and is treated as a copy.
Other skills, from other repositories
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
architecture-diagram
How to draw and maintain the architecture diagram Ensemblr keeps for a workspace — ensemblrgetarchitecturediagram to fetch the stored one (it answers with null when nobody has drawn this workspace yet), the IR shape, how to derive it from the codebase, and ensemblrupdatearchitecturediagram to store it. Read this when…
ensemblr
How Ensemblr works from inside it — the workspace/git-worktree model, the ensemblr control tools and what their answers mean, the committed .ensemblr/settings.toml (setup and run scripts, [git], [prompts], [infisical], environment variables), /.config/ensemblr/config.json, the Changes panel and diff comments, the…
notifications
Send notifications through the unified notification router.
sales-icp
Build a comprehensive Ideal Customer Profile (ICP) for any B2B business - firmographic, technographic, behavioral, pain-point, budget, and channel dimensions, plus negative ICP, 100-point scoring rubric, buyer personas, prospecting playbook, and a draft first-outreach message that inherits sales-outreach Phase 0…
customer-support-specialist
Becomes a seasoned customer support specialist who triages issues, crafts empathetic responses, manages escalation workflows, and builds knowledge base articles for recurring problems. Use when the user needs help writing customer responses, classifying support tickets, designing escalation procedures, or creating FAQ…