git_timestamps

git_timestamps is a cursor rule for Cursor from wiggitywhitney/mcp-commit-story. It costs 0 tokens per session (944 once invoked), scanned A, original, MIT.

A coding rule that uses the time recorded in Git commits instead of the computer's current clock whenever Git history is available.

In plain words
What is it for?
Apply it to logging, reports, data storage, and other operations that need timestamps in a Git-based project.
Why use it?
It keeps logs and stored dates aligned with the project's development timeline, rather than with when a command happens to run.

Cursor rule for Cursor

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/wiggitywhitney/mcp-commit-story/git_timestamps
Clone the repo
git clone --depth 1 https://github.com/wiggitywhitney/mcp-commit-story

Made for: Cursor.

Wrote 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.

agentmods badge for git_timestamps

README.md
[![agentmods](https://agentmods.dev/badge/rules/wiggitywhitney/mcp-commit-story/git_timestamps.svg)](https://agentmods.dev/rules/wiggitywhitney/mcp-commit-story/git_timestamps)
Your own site
<a href="https://agentmods.dev/rules/wiggitywhitney/mcp-commit-story/git_timestamps"><img src="https://agentmods.dev/badge/rules/wiggitywhitney/mcp-commit-story/git_timestamps.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 944 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00944
Opus 5 $0.00000 $0.00472
Sonnet 5 $0.00000 $0.00189
Haiku 4.5 $0.00000 $0.00094

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

Security

Grade A, and why

git_timestamps 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 3d 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.

.cursor/rules/git_timestamps.mdc · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Timestamp Consistency Rule

Always use git commit timestamps instead of current system time for logging, data storage, and operations throughout the system.

Core Principle

  • Use commit.committed_datetime or commit.committed_date from GitPython for all timestamp operations
  • Never use datetime.now(), time.time(), or other current-time functions when git context is available
  • Maintain temporal consistency with the actual development timeline

Implementation Patterns

✅ DO: Use Git Commit Timestamps

# For ISO format timestamps
timestamp = commit.committed_datetime.isoformat()

# For date strings  
date_str = commit.committed_datetime.strftime("%Y-%m-%d")

# For Unix timestamps
timestamp = commit.committed_date

# For datetime objects
dt = commit.committed_datetime

✅ DO: Access Latest Commit Timestamp

def get_git_commit_timestamp(repo_path: str) -> Optional[str]:
    """Get timestamp from most recent git commit."""
    try:
        repo = git.Repo(repo_path)
        if not repo.heads:
            return None
        latest_commit = repo.head.commit
        return latest_commit.committed_datetime.isoformat()
    except Exception:
        return None

✅ DO: Use in Logging with Fallback

def log_with_git_timestamp(message: str, repo_path: str = None):
    """Log with git commit timestamp for consistency."""
    timestamp = get_git_commit_timestamp(repo_path) if repo_path else None
    if timestamp:
        log_message = f"[{timestamp}] {message}"
    else:
        # Fallback only when git context unavailable
        log_message = f"[{datetime.now().isoformat()}] {message}"
    logger.info(log_message)

❌ DON'T: Use Current System Time When Git Context Available

# ❌ Wrong - ignores git timeline
timestamp = datetime.now().isoformat()
log_entry = f"[{datetime.now()}] Generated summary"

# ❌ Wrong - inconsistent with commit history
file_timestamp = time.time()

❌ DON'T: Mix Timestamp Sources

Read the full file on GitHub · 142 lines

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. 3d ago First seen · 142 lines · 0 tokens per session scan A 53fccc3d95f3

Subscribe to this mod's changes

git_timestamps is a cursor rule published in the GitHub repository wiggitywhitney/mcp-commit-story (15 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 944 tokens. 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.