Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add mishahanin/heading-os-marketplace/plugin install heading-intelWrote 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/mishahanin/heading-os-marketplace/market-brief)<a href="https://agentmods.dev/skills/mishahanin/heading-os-marketplace/market-brief"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os-marketplace/market-brief/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/mishahanin/heading-os-marketplace/market-brief"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os-marketplace/market-brief.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.00121 | $0.01238 |
| Opus 5.5 | $0.00048 | $0.00495 |
| Sonnet 5.5 | $0.00024 | $0.00248 |
| Haiku 4.5 | $0.00012 | $0.00124 |
Grade A, and why
market-brief 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 2mo 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-brief — 21 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Brief
Produce an instant market intelligence brief on a region, country, sector, or competitor.
Variables
topic: [Region / country / competitor / technology trend — e.g., "[target-region] telco market", "a competitor DPI position", "[region] sovereignty regulations", "5G security spending in [region]"]
depth: surface | detailed — default: surface (3-5 key points); detailed (full analysis)
purpose: [What decision or action this brief supports — optional]
Instructions
Before drafting, read:
reference/dpi-market-intelligence.md— DPI market data and competitor landscapereference/geopolitical-landscape.md— Regional sovereignty and tech contextreference/search-domains.md— Domain filtering for web searchescontext/strategy.md— Strategic priorities to frame relevancecontext/current-data.md— Current positioning and active markets
When searching the web for market intelligence, apply domain filtering from reference/search-domains.md:
- Use
allowed_domainsfrom the topic groups most relevant to the query. Telecom & DPI serves the DPI market, and the relevant regional group serves regional telecom - Always apply Blocked Domains as
blocked_domains - For broad market overview queries, use
blocked_domainsonly
Produce a brief covering:
Surface (3-5 key points):
- Market size and growth rate (if applicable)
- Key dynamics and drivers
- 31C's position and opportunity
- 2-3 actionable insights for Misha
Detailed (full analysis):
- All of the above plus:
- Competitive landscape in this region/sector
- Regulatory environment
- Entry timing assessment
- Recommended positioning approach
- Specific risks and mitigations
Frame everything through 31C's lens: sovereign, non-aligned, DPI+ category leader, the legacy incumbent vacuum opportunity.
Markets Are Pricing (conditional, Polymarket)
The Polymarket coverage whitelist is AI, big tech, elections, geopolitics, crypto, macro, global sports, and corporate events. See reference/polymarket-coverage.md. If the topic matches it, include a "Markets Are Pricing" section in the brief output.
What ships with it
1 file 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.
- 2mo ago First seen · 117 lines · 121 tokens per session scan A 4c554786ba9c
market-brief is a skill published in the GitHub repository mishahanin/heading-os-marketplace (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 121 tokens to every session and 1,238 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to market-brief, differing in 21 lines, and is treated as a copy.
Other skills, from other repositories
domain-modeling
Use when pinning down domain terminology, building a ubiquitous language or project glossary, disambiguating overloaded or vague terms, or maintaining a CONTEXT.md — or when another skill needs to sharpen the domain model. Do NOT use for recording architectural decisions or for writing implementation specs.
code-review
Iterative, human-in-the-loop code review that detects gaps, presents them for selection, and fixes them in cycles. Supports both diff-based PR review and holistic codebase analysis.
address-pr-review
Address reviewer and bot comments on a GitHub pull request — validate each comment, apply fixes where valid, reply with reasoning, and resolve threads.
interview
Deep requirements gathering through probing questions that surface hidden requirements, edge cases, and trade-offs before implementation.
ideate
Facilitate brainstorming as a thinking partner that extracts and expands latent ideas rather than generating them outright.
writing-artifacts
Use when writing or revising a durable written artifact — README, ADR, design doc, PR description, release notes, runbook, error message, user-facing docs. Gives a positive writing system (reader model, sentence positions, document jobs), not a ban-list. Do NOT use for conversational replies to the user (global…