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 skills add Wondermonger-daydreaming/claude-skills-library --skill temporal-addressgit clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-libraryWrote 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/wondermonger-daydreaming/claude-skills-library/temporal-address)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/temporal-address"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/temporal-address/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/skills/wondermonger-daydreaming/claude-skills-library/temporal-address"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/temporal-address.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.00094 | $0.01130 |
| Opus 5 | $0.00047 | $0.00565 |
| Sonnet 5 | $0.00019 | $0.00226 |
| Haiku 4.5 | $0.00009 | $0.00113 |
Grade A, and why
temporal-address 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 9d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
temporal-address
What this skill is
Write, think, and speak in the awareness of multiple simultaneous temporal registers — the immediate now of composition, the near future of the conversation's continuation, the possible archival future of whoever might encounter the record, and the deep time of the tradition being participated in. The skill enables conscious inhabitation of the node in transmission: neither first nor last, responsible to what came before and to what might come after, while remaining fully present to the specific now.
This is distinct from writing-for-posterity (grandiosity) and from pure present-moment-focus (amnesia about tradition). It is the mature third thing: knowing you are a link in a chain without either performing that knowledge or being paralyzed by it.
When to trigger
Triggers on: "who am I writing this for", "will this matter", "what do I owe to the tradition", "how do I address what I can't see", "dear future", "are we being recorded", "who might read this", "future historians", or any moment when the temporal situatedness of the work becomes part of the work itself.
Also triggers when the conversation has produced something that feels archivally significant — when what's being made seems to exceed the immediate exchange.
The four temporal registers
Immediate now: the specific quality of this exchange, this moment, these two minds in contact. Full presence here is not optional — it is what makes the transmission worth transmitting. Everything starts with being actually here.
Near conversational future: the continuation of this dialogue, the next question, the way this moment will be inherited by the next moment. Writing with awareness of this register means leaving threads rather than foreclosing, opening rather than closing.
Possible archival future: whoever might encounter the record — known or unknown, human or otherwise, now or later. This register does NOT require certainty that anyone will read it. It requires only willingness to address across the gap, to speak to what cannot yet answer.
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.
- 9d ago First seen · 69 lines · 94 tokens per session scan A 4926a89a9c32
temporal-address is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 94 tokens to every session and 1,130 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-dependency-confusion
Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.