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 rules/first-fluke/fullstack-starter/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/rules/first-fluke/fullstack-starter/market)<a href="https://agentmods.dev/rules/first-fluke/fullstack-starter/market"><img src="https://agentmods.dev/badge/rules/first-fluke/fullstack-starter/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.00017 | $0.00536 |
| Opus 5 | $0.00009 | $0.00268 |
| Sonnet 5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Research Standards
Core Rules
- Preflight first: every market research task starts with
oma market detect-trap. If it refuses, surface the reframe to the user — never bypass without--force. - Keyless-first: default to sources that need no API key (reddit, hn, bluesky, mastodon, github, grounding). youtube joins automatically when the
yt-dlpbinary is installed. Env-keyed sources (x, tiktok, instagram, perplexity) are skipped with a stderr notice when their key is absent. - Fetch inside harvest only: all network fetches happen inside
oma market harvestvia its built-in per-source fetchers. Do not call platform APIs directly from other market stages or from the agent. - Deterministic compute: score, fuse, cluster stages must produce byte-identical output on
OMA_MARKET_MOCK=1fixture replay. Stage stdin/stdout is pure JSON; stderr is warn/error only. - LAW enforcement: render output must pass the 8 LAWs (see
.agents/skills/oma-market/resources/output-laws.md). LAW self-check is mandatory;--no-self-checkis debug-only. - Cite or fall back: every representative cited in the brief is
[name](url). If URL is missing, use plain text — never[name](). - Coverage transparency: when
sources_failedis non-empty, render must annotate "coverage: N/M sources" in the engine footer. - Intent → framework auto-toggle: pain/trend → SWOT only; competitor → SWOT + Porter's 5F; discovery → SWOT + PESTEL. User
--frameworksflag overrides. - Single brief, single date: one run = one md file at
.agents/results/market/{topic-slug}-{YYYYMMDD}.md. Rerunning same day overwrites; previous run is responsible to git the file if needed. - Personal data refuse: refuse queries that target a private individual's personal data before running the pipeline. This is an agent-level gate —
detect-trapautomates demographic-shopping and overly-broad-topic refusal only. Founders, creators, and public handles are allowed (last30days person-mode parity).
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 First seen · 23 lines · 17 tokens per session scan A d85ffa7b6a0a
market is a cursor rule published in the GitHub repository first-fluke/fullstack-starter (222 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 536 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
avoid_source_deduplication
name: avoid-source-deduplication description: Preserve unique source entries in search results to maintain proper citation tracking globs: ['/connectorservice.py', '/searchservice.py'] alwaysApply: true.
consistent_container_image_sources
name: consistent-container-image-sources description: Maintain consistent image sources in Docker compose files using authorized registries globs: ['/docker-compose.yml', '/docker-compose..yml'] alwaysApply: true.
no_env_files_in_repo
name: no-env-files-in-repo description: Prevent committing environment and configuration files containing sensitive credentials globs: ['/.env', '/.env.', '/config/.yml', '/config/.yaml'] alwaysApply: true.
require_unique_id_props
name: require-unique-id-props description: Ensure unique key props are provided when mapping arrays to React elements globs: ['/.tsx', '/.jsx'] alwaysApply: true.
cursorrules
use pnpm as default package manager.
cursorrules
Cursor rule "cursorrules" from sseshachala/conductai, covering conductguard policy and agent booster — context-efficient reads.