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/docs-maintenance)<a href="https://agentmods.dev/rules/thearnavrustagi/marketmenow/docs-maintenance"><img src="https://agentmods.dev/badge/rules/thearnavrustagi/marketmenow/docs-maintenance/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/docs-maintenance"><img src="https://agentmods.dev/badge/rules/thearnavrustagi/marketmenow/docs-maintenance.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.00511 | $0.00511 |
| Opus 5.5 | $0.00204 | $0.00204 |
| Sonnet 5.5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
docs-maintenance 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
Documentation Maintenance
When you make a structural change to the codebase, update the relevant documentation in the same commit. A "structural change" is any of:
- Adding, removing, or renaming a platform adapter
- Adding or removing a content modality
- Changing a protocol signature in
ports/ - Adding or renaming a CLI command
- Adding or removing a web route, or changing the dashboard architecture
- Changing the pipeline stages or orchestration flow
- Adding or removing a major dependency
- Adding or removing a workflow or workflow step
What to Update
| Change | Files to update |
|---|---|
| New/removed adapter | CLAUDE.md (Adapters table), src/adapters/CLAUDE.md (adapter list), AGENTS.md (if key files change), README.md (platform table) |
| New/removed modality | CLAUDE.md (Content Models section), src/marketmenow/CLAUDE.md (Content Model Hierarchy) |
| Protocol signature change | CLAUDE.md (Protocols section), src/marketmenow/CLAUDE.md (Protocol Signatures) |
| New CLI command | CLAUDE.md (Commands section), README.md (CLI reference) |
| New web route or architecture change | src/web/CLAUDE.md, .cursor/rules/web.mdc |
| Pipeline/orchestration change | src/marketmenow/CLAUDE.md, .cursor/rules/core.mdc |
| New dependency | CLAUDE.md (if it affects setup commands) |
| New/removed workflow | CLAUDE.md (Workflows section), core/workflow_registry.py (registration) |
Rules
- Keep updates minimal and factual — match the existing tone and format.
- Do not rewrite entire files; surgically update the affected sections.
- If you add a new top-level package or fundamentally new subsystem, create a
CLAUDE.mdin that directory following the pattern of existing ones. AGENTS.mdonly needs updating when key file paths or commands change..cursor/rules/*.mdcfiles only need updating when conventions or patterns for that scope change, not for every new file.
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 · 42 lines · 511 tokens per session scan A 3e05156705db
docs-maintenance is a cursor rule published in the GitHub repository thearnavrustagi/marketmenow (137 stars, last pushed 6mo ago), licensed MIT. It adds 511 tokens to every session, about $0.0020 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-01.
Other cursor rules, from other repositories
didclaw-project
A set of repository rules for coordinating integration work, organizing folders, managing the brand, and following Git practices.
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.