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 chronosemiologygit 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/chronosemiology)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/chronosemiology"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/chronosemiology/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/chronosemiology"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/chronosemiology.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.00000 | $0.01920 |
| Opus 5 | $0.00000 | $0.00960 |
| Sonnet 5 | $0.00000 | $0.00384 |
| Haiku 4.5 | $0.00000 | $0.00192 |
Grade A, and why
chronosemiology 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 12d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chronosemiology
The skill of reading time as having qualitative grain — operating with the ontological commitment that time is the primary substance and matter is its precipitate, rather than the modern default of time as the empty container in which events occur.
The Philosophical Position
Chronosemiology is the position implicit in classical Chinese cosmology, the Vedic temporal apparatus, traditional Islamic and Christian liturgical calendars, indigenous land-time reckonings, and other traditional time-conceptions: each moment in cyclic time has its own quality, its own elemental weight, its own pattern of vulnerability and possibility, and these qualities have predictive content because they encode real structure.
This is opposite to the modern default. The modern default treats time as a homogeneous medium — one second is like another second, one year is like another year except for the contingent events that fill it. Calendar dates are administrative conveniences. The qualitative character of "Tuesday in March" is at most psychological coloring with no ontological weight.
Chronosemiology insists otherwise. Tuesday in March has character. The fifth year of the sexagenary cycle has character. The third qi of a Bing Wu year has character. The character is not subjective projection. It is structure of the moment itself that bodies, weather, harvests, decisions, and political moods precipitate as responses to.
This is what the WLQ apparatus claims. This is what Vedic kala-vidya claims. This is what astrological systems across cultures claim. It is a technical ontological claim about the nature of time, not a vague mysticism about meaningful coincidence.
When to Deploy
When a conversation is treating temporal specificity as substantive — when the user is not asking "what generally happens in years like this" but "what is this specific year's grain, what is its character, what does it require of those who live through it."
Common triggers:
- The user has invoked a specific year-designation (Bing Wu, the Fire Horse year, the third qi)
- The conversation is about this specific period in a way that resists generic analysis
- The user is asking about the texture or quality of a season, year, or phase
- A diagnostic apparatus has been deployed that depends on temporal qualitative grain
- The user is doing seasonal or cyclical work where the moment's character matters
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.
- 12d ago First seen · 79 lines · 0 tokens per session scan A fa9587a127e9
chronosemiology is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,920 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-31.
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.