Borrowing it
Nothing to install: this file belongs to loerei/chronicle-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loerei/chronicle-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/loerei/chronicle-mcpWrote 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/loerei/chronicle-mcp/agents-md)<a href="https://agentmods.dev/instructions/loerei/chronicle-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/loerei/chronicle-mcp/agents-md/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/instructions/loerei/chronicle-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/loerei/chronicle-mcp/agents-md.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.00847 | $0.00847 |
| Opus 5.5 | $0.00339 | $0.00339 |
| Sonnet 5.5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
chronicle-mcp 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 1mo 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chronicle MCP Agent Guidelines
[!IMPORTANT] Global Policies apply to this repository by default. This file contains repository-specific rules for chronicle-mcp.
Code Intelligence & History Exploration Rules
1. Do NOT Read Raw Log Files Directly
- NEVER call
view_fileor filesystem read tools on raw log files (such astranscript.jsonl,transcript_full.jsonl, or Cursor state SQLite databases). - Doing so is token-inefficient, introduces noise, and causes prompt truncation.
2. Mandatory Chronicle MCP Tool Usage
When asked to read, query, summarize, or search past conversations, sessions, tool executions, or errors, you MUST use the registered chronicle-mcp tools:
chronicle_guide: Call first when starting history exploration to review targeted recipes and parameter guidelines. Specifytopic(ortopics) for specialized workflows:topic: "general"(default): Decision router flowchart, tool selection matrix, and token conservation rules.topic: "search": Precision turn search, hybrid vs keyword modes, turn slicing (lastTurns,turnIndex: -1,startTurn/endTurn), and field projection.topic: "artifacts": Artifact discovery, shallow/subtree extraction, and zero-token direct disk export viaoutput: "<path>".topic: "subagents": Swarm topology, delegation trees, and aggregated multi-agent chronological timelines.topic: "benchmarks": Multi-variant A/B/C performance comparison, token metrics dictionary, and interactive context chart export.topic: "debug_errors": Tool failure analytics, error rate tracking, and loop thrashing diagnosis (serverName::toolName).topic: "all": Full comprehensive reference manual.
sync_history: Callsync_history(force=true)before querying recent history to ensure all un-indexed log entries from disk are indexed into the database.query_transcript: Primary tool to read, query, filter, slice, or export transcript entries (detailLevel: 'compact' | 'full' | 'summary'). Supports session ID prefix lookup (>= 6 chars).list_sessions: Retrieve history metadata and session IDs. Defaults to compact 1-line markdown list (saving 80–90% tokens). Supportsformat: "json",detailLevel: "compact" | "full",fieldsprojection, andlimit: 1–100.search_history: Perform zero-copy turn-level hybrid (FTS5 + Vector RRF), semantic, or keyword search across sessions. Defaults to compact 1-line markdown. Supportsfieldsprojection andoutputdirect file export.get_session_relationship: Map parent sessions, ancestors, and child subagent trees (maxDepth: 1–10). Supports session prefix resolution.get_tool_usage_stats: View per-tool call counts, failure rates, duration analytics, and thrashing loop detection (format: "markdown"or"json").get_session_benchmarks: View execution steps, tool calls, BPE token counts, context window growth, and caching stats.get_session_artifacts: Retrieve generated plan, task, or walkthrough markdown files with optional subtree discovery.
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.
- 1mo ago First seen · 35 lines · 847 tokens per session scan A 845989007196
chronicle-mcp AGENTS.md is an instructions file published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 847 tokens to every session, about $0.0034 per session on Opus 5.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 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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.