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.
git clone --depth 1 https://github.com/thearnavrustagi/marketmenowWrote 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/thearnavrustagi/marketmenow/web)<a href="https://agentmods.dev/rules/thearnavrustagi/marketmenow/web"><img src="https://agentmods.dev/badge/rules/thearnavrustagi/marketmenow/web/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/rules/thearnavrustagi/marketmenow/web"><img src="https://agentmods.dev/badge/rules/thearnavrustagi/marketmenow/web.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.00000 | $0.00499 |
| Opus 5.5 | $0.00000 | $0.00200 |
| Sonnet 5.5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
web 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.
What it actually says
Web Dashboard Rules
Architecture
The web app spawns mmn CLI commands as subprocesses — it does not call the
Python pipeline directly. cli_runner.py handles subprocess execution and
progress parsing. Real-time updates flow through EventHub → WebSocket.
Adapter CLIs are mounted as hidden groups in marketmenow/cli.py
(hidden=True). They don't appear in mmn --help but remain callable by the
web frontend. New workflows (like reddit-launch) use mmn run <name> directly.
Key Modules
app.py— FastAPI app with lifespan (DB pool + queue worker), WebSocket at/ws/content/{item_id}, route registration, static/output mounts.cli_runner.py—run_cli()andrun_cli_streaming(). DefinesPLATFORM_META(JSON params) andBUILDERS(command constructors). Progress parsed via regex.queue_worker.py—run_queue_loop()background task. Polls DB queue, checks per-platform rate limits, callsrun_cli_streamingfor each job.events.py—EventHubpub/sub per content-item UUID.ProgressEventtypes:phase,progress,wait,log,stderr,done,error.db.py— asyncpg pool, all DB operations (content, queue, rate limits, post log).
Patterns
- Routes live in
routes/as separateAPIRouterinstances. - Templates are Jinja2 in
templates/. - Static assets in
static/(CSS, JS). - Generated output mounted at
/outputfromsettings.output_dir.
Adding a Platform to the Dashboard
- Add an entry to
PLATFORM_METAincli_runner.py(label, modality, params). - Write generate and publish
CommandBuilderfunctions. - Register them in the
BUILDERSdict. - No route changes needed — the generate page auto-discovers from
PLATFORM_META.
Database
PostgreSQL via asyncpg. Pool initialized in lifespan, closed on shutdown.
MMN_WEB_DATABASE_URL env var required.
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 · 49 lines · 0 tokens per session scan A f4106adc30c6
web is a cursor rule published in the GitHub repository thearnavrustagi/marketmenow (137 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 499 tokens. 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-01.
Other cursor rules, from other repositories
didclaw-security
A set of security and TypeScript rules for Tauri applications. Tauri is a framework for building desktop apps with web technologies and Rust.
didclaw-client
A set of Cursor instructions for the didclaw client, called lclaw-ui. Cursor rules are project guidance that tell the coding agent about the codebase, commands, implementation practices, and release notes.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.