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/sfc-gh-abannerjee/snowgram/no-progress-mdsgit clone --depth 1 https://github.com/sfc-gh-abannerjee/SnowGramWrote 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/sfc-gh-abannerjee/snowgram/no-progress-mds)<a href="https://agentmods.dev/rules/sfc-gh-abannerjee/snowgram/no-progress-mds"><img src="https://agentmods.dev/badge/rules/sfc-gh-abannerjee/snowgram/no-progress-mds.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.00347 | $0.00347 |
| Opus 5 | $0.00173 | $0.00173 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
no-progress-mds 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 5d 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
Progress Tracking Rule
NEVER create new .md files for progress summaries, status updates, or completion reports.
Instead:
- Update the chat directly - Provide summaries inline in your response
- Update MILESTONES.md - Add new milestones with detailed timestamps
- Auto-cleanup - After generating files, check the root directory and archive any old progress/status .md files to
/archive/docs/
Timestamp Format for MILESTONES.md
### Milestone X: [Title] ✅
**Date**: YYYY-MM-DD HH:MM PST
**Duration**: X hours
**Impact**: [Critical/High/Medium/Low]
Exceptions (allowed .md files in root):
- README.md, CONTRIBUTING.md, LICENSE, QUICKSTART.md, MILESTONES.md
- PRODUCTION_READINESS_COMPLETE.md, IMPLEMENTATION_SUMMARY.md, SPCS_BEST_PRACTICES_AUDIT.md
- .github/ templates (bug reports, feature requests)
Files to Archive Automatically:
*_STATUS.md, *_COMPLETE.md, PROGRESS.md, SUMMARY.md, SUCCESS.md, SESSION.md, BUILD.md, DEPLOYMENT.md
Cleanup After Any File Generation:
find . -maxdepth 1 -name "*_*.md" | grep -v "PRODUCTION\|IMPLEMENTATION\|SPCS_BEST" | while read f; do mv "$f" archive/docs/; done
Maximum 10 .md files in root. Archive anything beyond production-necessary documentation.
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.
- 5d ago First seen · 35 lines · 347 tokens per session scan A b8b82187d449
no-progress-mds is a cursor rule published in the GitHub repository sfc-gh-abannerjee/SnowGram (2 stars, last pushed 2mo ago), licensed MIT. It adds 347 tokens to every session, about $0.0017 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-08-31.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.