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 gracefullight/docusaurus-plugins --skill oma-marketgit clone --depth 1 https://github.com/gracefullight/docusaurus-pluginsWrote 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/gracefullight/docusaurus-plugins/oma-market)<a href="https://agentmods.dev/skills/gracefullight/docusaurus-plugins/oma-market"><img src="https://agentmods.dev/badge/skills/gracefullight/docusaurus-plugins/oma-market/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/gracefullight/docusaurus-plugins/oma-market"><img src="https://agentmods.dev/badge/skills/gracefullight/docusaurus-plugins/oma-market.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.00105 | $0.02725 |
| Opus 5.5 | $0.00042 | $0.01090 |
| Sonnet 5.5 | $0.00021 | $0.00545 |
| Haiku 4.5 | $0.00011 | $0.00272 |
Grade A, and why
oma-market 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Research Agent - Community Signal Intelligence
Scheduling
Goal
Classify user intent into pain / trend / competitor / discovery, fan-out to community sources via oma search fetch, score and cluster findings with deterministic CLI compute, auto-apply strategic frameworks, and emit a single LAW-compliant markdown brief.
Intent signature
- User asks about pain points, user complaints, or voice-of-customer signals for a product or category.
- User asks what is trending, growing, or declining in a space this week or month.
- User asks how one product compares to another in community sentiment or positioning.
- User asks for discovery or exploratory market research on a topic.
When to use
- Extracting real user pain points from community posts (Reddit, HN, GitHub Issues, Bluesky, Mastodon)
- Detecting trends in a product category over a time window (7d / 30d / 90d / 180d)
- Competitor sentiment analysis and SWOT positioning
- Open-ended discovery research across multiple sources
When NOT to use
- General web research without market framing -> use oma-search directly
- Single-source queries only -> use
oma search fetchstandalone - Delta tracking or trend velocity over time (v2 feature) -> defer
- Live dashboards or scheduled monitoring -> out of scope (v1 one-shot only)
Expected inputs
- Topic string and optional
--intent pain|trend|competitor|discovery - Optional
--window 7d|30d|90d|180d(default:30d) - Optional
--sources <list>to override defaults - Optional
--vs <entity>for competitor COMPARISON mode - Optional
--frameworks auto|none|swot,5f,pestel
Expected outputs
- Single markdown brief at
.agents/results/market/{topic-slug}-{YYYYMMDD}.md - Badge first-line,
What we learned:body opener (or COMPARISON title), engine footer - No raw evidence dump; no Sources block; no em-dash; no
##in body (framework/COMPARISON sections excepted)
Dependencies
oma-searchfor all fetches (oma search fetch --only api); never fetches directly- Serena
trust-registry-cache(read-only); Trust Registry labels inherited from oma-search resources/intent-rules.md,resources/operator-packs/,resources/output-laws.md
What ships with it
13 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.
- resources/checklist.md 1.2 KB
- resources/error-playbook.md 2.5 KB
- resources/examples.md 9.3 KB
- resources/execution-protocol.md 4.0 KB
- resources/frameworks/pestel.md 2.9 KB
- resources/frameworks/porters-5f.md 2.9 KB
- resources/frameworks/swot.md 2.5 KB
- resources/intent-rules.md 3.1 KB
- resources/operator-packs/competitor.md 1.3 KB
- resources/operator-packs/discovery.md 1.2 KB
- resources/operator-packs/pain.md 1.4 KB
- resources/operator-packs/positive.md 1.2 KB
- resources/output-laws.md 5.4 KB
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 · 194 lines · 105 tokens per session scan A 8f63048aaa70
oma-market is a skill published in the GitHub repository gracefullight/docusaurus-plugins (23 stars, last pushed 27d ago), licensed MIT. It adds 105 tokens to every session and 2,725 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other skills, from other repositories
claude-code-dmwork
Connect to DMWork messaging platform as an AI bot via the OpenClaw DMWork adapter plugin.
vs-chat
Conversational search runtime: send messages, keep sessions consistent, and verify retrieval behavior and responses.
cometchat-android-v6-core
Foundational rules for the CometChat Android UI Kit v6 — the two UI cohorts and their artifacts, credentials via the gitignored assets settings file, initFromSettings → login → render ordering, the component map, and the production-ready core chat surface. Read this first for any Android CometChat task. Triggers…
cometchat-react-v7-core
Add CometChat chat to a React app end-to-end — detect the project, get & verify dashboard credentials, init→login→render with CometChatProvider, and the drop-in conversation UI. The core knowledge every other React v7 skill builds on. Triggers: 'add chat to my react app', 'integrate cometchat react', 'set up cometchat…
cometchat-android-v6-compose-placement
Where the CometChat Android v6 chat UI goes in a Jetpack Compose app — the default conversations→message NavHost flow, growing to the tab-based app (chats/users/groups/calls + detail, thread and search routes + incoming calls), a single one-to-one screen, or chat embedded in an existing composable, with a correct back…
cometchat-android-v5-sdk
Build chat on Android with the headless CometChat Chat SDK v5 and your OWN UI — init/login ordering, the method map, request-builder pagination, listener lifecycle, and a production-ready app surface (optimistic updates, error states, sized shell). Use when the app needs custom UI instead of the drop-in UI Kit.…