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 instructions/hodgesmr/temporal-awareness/agents-mdgit clone --depth 1 https://github.com/hodgesmr/temporal-awarenessWrote 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/instructions/hodgesmr/temporal-awareness/agents-md)<a href="https://agentmods.dev/instructions/hodgesmr/temporal-awareness/agents-md"><img src="https://agentmods.dev/badge/instructions/hodgesmr/temporal-awareness/agents-md.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.00450 | $0.00450 |
| Opus 5 | $0.00225 | $0.00225 |
| Sonnet 5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
temporal-awareness AGENTS.md 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 4d 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
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Purpose
This repository contains a Claude Code skill called "temporal-awareness" that ensures temporal accuracy by using Unix date commands. The skill should be invoked whenever Claude needs date/time information: current date, day of week calculations, date arithmetic, or deadline computations.
Structure
skills/temporal-awareness/SKILL.md # Skill definition and documentation
Key Concepts
- GNU vs BSD date: The skill handles both GNU date (Linux) and BSD date (macOS/FreeBSD), which have different syntax for date parsing and arithmetic
- Trigger conditions: Use this skill when users ask about dates, days of week, deadlines, durations, or any temporal context
- Verification first: Always run
datecommands before responding to date-sensitive queries, as Claude's system prompt date may be stale
Releases
Releases use semver tags (e.g., 1.0.0) plus a latest tag that always points to the most recent stable release.
Release Process
- Update the version in
skills/temporal-awareness/SKILL.mdfrontmatter:metadata: author: Matt Hodges version: "1.1.0" - Update
CHANGELOG.md:- Add a new section at the top (below the header) for the new version
- Use the format
## [X.Y.Z] - YYYY-MM-DD - Document changes under
### Added,### Changed,### Fixed, or### Removedas appropriate - Add a comparison link at the bottom:
[X.Y.Z]: https://github.com/hodgesmr/temporal-awareness/compare/PREV...X.Y.Z
- Commit the version bump and changelog update
- Run the release script:
./release.sh
The script extracts the version from SKILL.md, creates the version tag, updates the latest tag, and pushes both.
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.
- 4d ago First seen · 45 lines · 450 tokens per session scan A 45e2856a2011
temporal-awareness AGENTS.md is an instructions file published in the GitHub repository hodgesmr/temporal-awareness (10 stars, last pushed 7mo ago), licensed MIT. It adds 450 tokens to every session, about $0.0022 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.