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 skills/vladolaru/claude-code-plugins/current-datetimenpx skills add vladolaru/claude-code-plugins --skill current-datetimegit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWrote 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/skills/vladolaru/claude-code-plugins/current-datetime)<a href="https://agentmods.dev/skills/vladolaru/claude-code-plugins/current-datetime"><img src="https://agentmods.dev/badge/skills/vladolaru/claude-code-plugins/current-datetime.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.00107 | $0.01221 |
| Opus 5 | $0.00053 | $0.00611 |
| Sonnet 5 | $0.00021 | $0.00244 |
| Haiku 4.5 | $0.00011 | $0.00122 |
Grade A, and why
current-datetime 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Current Date/Time
RULE 0: Always Verify
Run date BEFORE:
- Writing any date or time value into a file (
Last updated, document metadata, timestamps in code) - Stating the current date or time in a response
- Calculating staleness, age, or time remaining
- Any reasoning where "right now" is a fact you depend on
Never assume. The system prompt date is a snapshot from conversation start — it may be stale. The system prompt has NO time at all. Trust date output, not memory or inference.
Most Common Command
date +"%Y-%m-%d %H:%M" # 2026-03-17 14:39 — for Last updated headers
Quick Reference: Date
| Task | GNU date (Linux) | BSD date (macOS) |
|---|---|---|
| Current date | date +%Y-%m-%d |
date +%Y-%m-%d |
| Day of week | date +%A |
date +%A |
| Specific date's day | date -d "2025-03-15" +%A |
date -j -f "%Y-%m-%d" "2025-03-15" +%A |
| Add days | date -d "+7 days" +%Y-%m-%d |
date -v +7d +%Y-%m-%d |
| Days between | echo $(( ($(date -d "2025-12-31" +%s) - $(date -d "2025-01-01" +%s)) / 86400 )) |
echo $(( ($(date -j -f "%Y-%m-%d" "2025-12-31" +%s) - $(date -j -f "%Y-%m-%d" "2025-01-01" +%s)) / 86400 )) |
Quick Reference: Time
| Task | GNU date (Linux) | BSD date (macOS) |
|---|---|---|
| Current time (24h) | date +%H:%M:%S |
date +%H:%M:%S |
| Full datetime | date +"%Y-%m-%d %H:%M:%S" |
date +"%Y-%m-%d %H:%M:%S" |
| ISO 8601 | date -Iseconds |
date +%Y-%m-%dT%H:%M:%S%z |
| Unix timestamp | date +%s |
date +%s |
| From timestamp | date -d @1704067200 |
date -r 1704067200 |
| Add hours | date -d "+3 hours" |
date -v +3H |
| Time in other TZ | TZ="America/New_York" date |
TZ="America/New_York" date |
Common Time Zones
| Region | TZ Identifier | UTC Offset |
|---|---|---|
| Pacific (US/Canada) | America/Los_Angeles |
UTC-8/-7 |
| Mountain (US/Canada) | America/Denver |
UTC-7/-6 |
| Central (US/Canada/Mexico) | America/Chicago |
UTC-6/-5 |
| Eastern (US/Canada) | America/New_York |
UTC-5/-4 |
| South America East | America/Sao_Paulo |
UTC-3 |
| Western Europe (UK/PT) | Europe/London |
UTC+0/+1 |
| Central Europe (DE/FR/IT/ES) | Europe/Paris |
UTC+1/+2 |
| Eastern Europe (RO/BG/GR/UA/FI) | Europe/Bucharest |
UTC+2/+3 |
| Gulf (UAE/Oman) | Asia/Dubai |
UTC+4 |
| South Africa | Africa/Johannesburg |
UTC+2 |
| India | Asia/Kolkata |
UTC+5:30 |
| Southeast Asia (SG/MY/PH) | Asia/Singapore |
UTC+8 |
| China / Hong Kong | Asia/Shanghai |
UTC+8 |
| Japan / Korea | Asia/Tokyo |
UTC+9 |
| Australia East | Australia/Sydney |
UTC+10/+11 |
| New Zealand | Pacific/Auckland |
UTC+12/+13 |
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.
- yesterday First seen · 83 lines · 107 tokens per session scan A c31d3b34d911
current-datetime is a skill published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 1,221 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…