pn-current-date

A rule for using a specific calendar date when writing time-sensitive text such as changelogs or “as of” statements.

In plain words
What is it for?
Use it when writing changelog entries, copyright years, dated notes, or other claims that depend on the current date.
Why use it?
It prevents dates from being guessed from filenames, local assumptions, or an unreliable clock.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/perniemann/pncore/pn-current-date
Clone the repo
git clone --depth 1 https://github.com/perniemann/pnCore
Per session 212 This file is loaded in full into every session.
When invoked 212 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00212 $0.00212
Opus 5 $0.00106 $0.00106
Sonnet 5 $0.00042 $0.00042
Haiku 4.5 $0.00021 $0.00021

Measured 2d ago against content hash b1f1f6870035, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pn-current-date 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 2d 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.

packages/pn-core-mcp/content/rules/pn-current-date.mdc · 14 lines

What it actually says

Current date (plugin + MCP)

When you write CHANGELOG entries, "as of [date]", copyright years, or other calendar-sensitive text:

  1. If the pn-core MCP health tool is available: Call it and use calendarDateUtc (YYYY-MM-DD) for the calendar day at the server, and timestampUtc when a full ISO instant is appropriate. The server clock is the single source of truth for "today" in that session.
  2. If MCP is not connected: Use the date the user or environment provides (e.g. Cursor user_info "Today's date" when present). If none is given and the task requires a date, ask once instead of guessing.

Do not infer the month or year from filenames or document titles alone.

Changes

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.

  1. 2d ago First seen · 14 lines · 212 tokens per session scan A b1f1f6870035

Subscribe to this mod's changes

pn-current-date is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed 3d ago), licensed MIT. It adds 212 tokens to every session, about $0.0011 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.