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 agentmods add skills/first-fluke/fullstack-starter/oma-marketnpx skills add first-fluke/fullstack-starter --skill oma-marketgit clone --depth 1 https://github.com/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/oma-market)<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-market"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-market.svg" alt="Measured on agentmods" 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 | $0.00152 | $0.02287 |
| Opus 5 | $0.00076 | $0.01144 |
| Sonnet 5 | $0.00030 | $0.00457 |
| Haiku 4.5 | $0.00015 | $0.00229 |
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 today.
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 oma-market — 0 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 — 132 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
Run the upstream last30days research engine (always the latest release, managed by oma) for community-signal research, then frame the result for the user's intent (pain / trend / competitor / discovery) with strategic frameworks and save one brief under .agents/results/market/.
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, a person, a company, or a ticker.
When to use
- Extracting real user pain points from community posts (Reddit with real upvotes and top comments, HN, X, Bluesky, GitHub Issues)
- Detecting trends in a category over a window (
--days 7|30|90|180) - Competitor sentiment analysis and SWOT / Porter's 5F positioning
- Open-ended discovery research (
--discover), person mode, hiring signals (--hiring-signals), follow-up drills (--drill)
When NOT to use
- General web research without market framing -> use oma-search directly
- Academic literature -> use oma-scholar
- Live dashboards or scheduled monitoring ->
oma schedule:*wrapping this skill
Expected inputs
- Topic string; optional
--intent pain|trend|competitor|discovery(else classified perresources/intent-rules.md) - Optional window (
--days),--vs <entity>(competitor),--frameworks auto|none|swot,5f,pestel - Any native last30days flag (see
oma market run --help) — passed through verbatim
Expected outputs
- Single markdown brief at
.agents/results/market/{topic-slug}-{YYYYMMDD}.md - First line: the engine's badge (
🌐 last30days v{VERSION} · synced {date}); body per the upstream OUTPUT CONTRACT; framework sections appended per intent; engine footer preserved - Raw engine artifacts under
market.save_dir(default.agents/results/market/raw/)
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 876 B
- resources/error-playbook.md 1.4 KB
- resources/examples.md 11 KB
- resources/execution-protocol.md 2.5 KB
- resources/frameworks/pestel.md 2.8 KB
- resources/frameworks/porters-5f.md 2.8 KB
- resources/frameworks/swot.md 2.4 KB
- resources/intent-rules.md 2.4 KB
- resources/operator-packs/competitor.md 1.3 KB
- resources/operator-packs/discovery.md 1.6 KB
- resources/operator-packs/pain.md 1.4 KB
- resources/operator-packs/positive.md 1.3 KB
- resources/output-laws.md 2.2 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.
- today Changed · -62 lines · +47 tokens per session 195597515e00
- yesterday First seen · 194 lines · 105 tokens per session scan A a77448b7734a
oma-market is a skill published in the GitHub repository first-fluke/fullstack-starter (222 stars, last pushed yesterday), licensed MIT. It adds 152 tokens to every session and 2,287 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to oma-market, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
rag-knowledge
Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…
alembic-migration
Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
billing-stripe
Work with Stripe billing — subscriptions, plans/prices, the Customer Portal, credits, usage metering, invoices, and webhook events. Use when changing plans, handling a new Stripe webhook, debugging a payment/subscription flow, or touching credit balances and usage.