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/kyanitelabs/epoch/agents-mdgit clone --depth 1 https://github.com/KyaniteLabs/EpochWrote 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/kyanitelabs/epoch/agents-md)<a href="https://agentmods.dev/instructions/kyanitelabs/epoch/agents-md"><img src="https://agentmods.dev/badge/instructions/kyanitelabs/epoch/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.00648 | $0.00648 |
| Opus 5 | $0.00324 | $0.00324 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
Epoch 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epoch agent contract
Epoch is a TypeScript MCP server for structured time estimation, temporal math, analytics, cost, risk, and estimate-vs-actual feedback.
Commands and public skill
pnpm run build— tsup bundlepnpm test— Vitestpnpm run typecheck— TypeScript checknode canary-runner.mjs— function-calling canaryskills/epoch/SKILL.mdis the public agent skill; keep it aligned with the MCP tool list, CLI commands, and feedback-token workflow.
Architecture
src/index.ts— stdio MCP entry pointsrc/dispatcher/— tool registry and routingsrc/schemas/— centralized Zod schemassrc/lib/— pure business logic for estimation, temporal, analytics, cost, risk, profiles, calendar, feedback, self-improvement, and telemetrysrc/tools/— MCP registrationsrc/data/— reference databases
Schemas and tool registrations are shared hot paths. Register tools through the existing server pattern; keep library code independent of MCP concerns. Use co-located Vitest tests and preserve the estimate-vs-actual feedback contract.
Do not put current tool counts, provider endpoints, quotas, release state, or task status in this file. Preserve dirty work, verify current branch/remote/CI and runtime state, and run focused checks before claims. Stop before external, credentialed, public, financial, or destructive actions without approval.
Empower the Orchestrator
This repository is governed by the Empower Orchestrator law. Every top-level/orchestrator agent session is an audition to improve the system, not only finish the current task.
When you notice a repeatable task done 3+ times or a recurring agent failure mode, consider shipping the smallest durable artifact that prevents the repetition: a tool, skill, slash command, hook, guardrail, memory entry, test, verifier, or doctrine doc.
This applies to top-level/orchestrator sessions. Background workers execute their assigned slice and do not independently widen scope.
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 · 58 lines · 648 tokens per session scan A bb33bee11035
Epoch AGENTS.md is an instructions file published in the GitHub repository KyaniteLabs/Epoch (7 stars, last pushed 2d ago), licensed Apache-2.0. It adds 648 tokens to every session, about $0.0032 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
lean-pm-skills CLAUDE.md
Claude Code instructions for mrthames/lean-pm-skills, covering lean pm skills for claude code, setup, core principles, 1. start with the problem, not the solution and 2. write for builders.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.
mcp-execution mcp-wasm-runtime.instructions.md
Instructions for bug-ops/mcp-execution, covering copilot instructions: mcp-wasm-runtime, security - critical, security principles, security configuration and host function safety.