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/drumnation/unsplash-smart-mcp-server/date-time.rulesgit clone --depth 1 https://github.com/drumnation/unsplash-smart-mcp-serverWrote 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/drumnation/unsplash-smart-mcp-server/date-time.rules)<a href="https://agentmods.dev/rules/drumnation/unsplash-smart-mcp-server/date-time.rules"><img src="https://agentmods.dev/badge/rules/drumnation/unsplash-smart-mcp-server/date-time.rules.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.00273 | $0.00273 |
| Opus 5 | $0.00137 | $0.00137 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
date-time.rules 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
Date Command Usage:
# For full timestamps (ALWAYS use this format for document headers and meeting notes):
date +'%A, %B %d, %Y at %I:%M:%S %p'
# For date-only fields:
date +'%Y-%m-%d'
# For log timestamps:
date +'%Y-%m-%d %H:%M:%S'
Common Scenarios Requiring Date Generation:
- Creating/updating documents
- Writing meeting notes
- Setting "Last Updated" timestamps
- Recording creation dates
- Dating project milestones
- Setting review dates
- Adding timestamps to logs
Validation Steps:
Before completing ANY task involving dates:
- Search for date fields that need updating
- Run date command for each field
- Update ALL dates using command output
- Verify no hardcoded dates remain
Examples:
✅ CORRECT:
# Meeting Notes
## $(date +'%A, %B %d, %Y at %I:%M:%S %p')
❌ INCORRECT:
- Copying dates from other files
- Using hardcoded dates
- Leaving dates unchanged
- Making assumptions about current date
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 · 46 lines · 273 tokens per session scan A 7f9dc902d41f
date-time.rules is a cursor rule published in the GitHub repository drumnation/unsplash-smart-mcp-server (63 stars, last pushed 7mo ago), licensed MIT. It adds 273 tokens to every session, about $0.0014 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-30.
Other cursor rules, from other repositories
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.
family-instance-domain-actions
Family instance domain action implementation 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.