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/PaulJPhilp/EffectPatternsWrote 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/pauljphilp/effectpatterns/beyond-the-date-type-real-world-dates-times-and-timezones)<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/beyond-the-date-type-real-world-dates-times-and-timezones"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/beyond-the-date-type-real-world-dates-times-and-timezones/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/pauljphilp/effectpatterns/beyond-the-date-type-real-world-dates-times-and-timezones"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/beyond-the-date-type-real-world-dates-times-and-timezones.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.00509 | $0.00509 |
| Opus 5 | $0.00254 | $0.00254 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
beyond-the-date-type---real-world-dates-times-and-timezones 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Use the Clock service for testable time-based logic and immutable primitives for timestamps. globs: "**/*.ts" alwaysApply: true
Beyond the Date Type - Real World Dates, Times, and Timezones
Rule: Use the Clock service for testable time-based logic and immutable primitives for timestamps.
Example
This example shows a function that creates a timestamped event. It depends on the Clock service, making it fully testable.
import { Effect, Clock } from "effect";
import type * as Types from "effect/Clock";
interface Event {
readonly message: string;
readonly timestamp: number; // Store as a primitive number (UTC millis)
}
// This function is pure and testable because it depends on Clock
const createEvent = (
message: string
): Effect.Effect<Event, never, Types.Clock> =>
Effect.gen(function* () {
const timestamp = yield* Clock.currentTimeMillis;
return { message, timestamp };
});
// Create and log some events
const program = Effect.gen(function* () {
const loginEvent = yield* createEvent("User logged in");
yield* Effect.log("Login event:", loginEvent);
const logoutEvent = yield* createEvent("User logged out");
yield* Effect.log("Logout event:", logoutEvent);
});
// Run the program
const programWithErrorHandling = program.pipe(
Effect.provideService(Clock.Clock, Clock.make()),
Effect.catchAll((error) =>
Effect.gen(function* () {
yield* Effect.logError(`Program error: ${error}`);
return null;
})
)
);
Effect.runPromise(programWithErrorHandling);
Explanation:
JavaScript's native Date object is a common source of bugs. It is mutable, its behavior can be inconsistent across different JavaScript environments (especially with timezones), and its reliance on the system clock makes time-dependent logic difficult to test.
Effect's approach solves these problems:
- The
Clockservice abstracts away the concept of "now." In production, theLiveclock uses the system time. In tests, you can provide aTestClockthat gives you complete, deterministic control over the passage of time. - Using primitive
numberorstringfor timestamps ensures immutability and makes your data easy to serialize, store, and transfer.
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.
- 11d ago First seen · 65 lines · 509 tokens per session scan A 7671273bfea8
beyond-the-date-type---real-world-dates-times-and-timezones is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (798 stars, last pushed 2mo ago), licensed MIT. It adds 509 tokens to every session, about $0.0025 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
typescript-code-generation-rules
Rules for generating TypeScript code in Next.js 14 components, including component definition syntax, props definitions, and named/default exports.
typescript-coding-style
Enforces code style and best practices for TypeScript files.
react-and-typescript-general-rules
General rules for React and TypeScript projects, focusing on code clarity and best practices.
javascript-typescript-code-style
Rules for JavaScript and TypeScript code style, including modern features, functional patterns, and descriptive naming conventions.
code-style-and-improvements
This rule focuses on code style, refactoring suggestions, and leveraging the latest ES and Node.js features for JavaScript, TypeScript, and Python files.
key-conventions
Key coding conventions for Astro projects including style guide and typescript.