agentmods.dev

chronolog: Instructions file for Claude Code

CLAUDE.md

chronolog CLAUDE.md is an instructions file for Claude Code from grc-iit/chronolog. It costs 2,955 tokens per session, scanned A, original, BSD-2-Clause.

Project instructions for ChronoLog, a distributed system for storing event logs across multiple machines and storage layers.

In plain words
What is it for?
They help with ChronoLog development, including its deployment scripts, distributed services, container or cluster setup, and end-to-end test loop.
Why use it?
They give the coding agent the project's required build, deployment, and testing procedures instead of leaving those choices unclear.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is grc-iit/chronolog's own configuration. It tells Claude Code how to work on chronolog itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything chronolog configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/kfeng/CLionProjects/ChronoLog_dev/latest/ChronoLog.

not rated 15repo 2d ago A scan 2,955 tokens original BSD-2-Clause
View source ↗ grc-iit/chronolog chronolog.dev
Reuse

Borrowing it

Nothing to install: this file belongs to grc-iit/chronolog. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/grc-iit/chronolog/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/grc-iit/chronolog

Made for: Claude Code.

Wrote 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.

agentmods badge for chronolog CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/grc-iit/chronolog/claude-md/github.svg)](https://agentmods.dev/instructions/grc-iit/chronolog/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/grc-iit/chronolog/claude-md"><img src="https://agentmods.dev/badge/instructions/grc-iit/chronolog/claude-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.

agentmods 80×15 button for chronolog CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/grc-iit/chronolog/claude-md"><img src="https://agentmods.dev/badge/instructions/grc-iit/chronolog/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,955 This file is loaded in full into every session.
When invoked 2,955 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02955 $0.02955
Opus 5 $0.01477 $0.01477
Sonnet 5 $0.00591 $0.00591
Haiku 4.5 $0.00296 $0.00296

Measured 2d ago against content hash 861fe3ba070b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

chronolog CLAUDE.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 2d 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.

CLAUDE.md · 245 lines

How it starts

The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — ChronoLog dev notes

Project-specific instructions for Claude. The single source of truth for the build/install/deploy/bench loop is the deploy script set under tools/deploy/. Always go through these scripts; do not invoke cmake/make directly.

System overview

ChronoLog is a distributed log storage ecosystem that uses physical time as the ordering mechanism - eliminating centralized sequencers and enabling auto-tiered storage across multiple layers. Built to capture the velocity and variety of modern activity data: from scientific instruments producing terabytes per second to AI agent audit trails.

Deployment modern

ChronoLog is expected to be deployed in a distributed environment, either on a cluster with multiple physical nodes or a swarm of containers. Each service component (i.e., ChronoVisor, ChronoKeeper, ChronoGrapher and ChronoPlayer) is preferred to run on a dedicated node/container. Co-located services are possible too. Client apps may co-located with ChronoKeeper nodes. All nodes (services and client apps) share a global file system. It could be a NFS (v3 or v4), or a Parallel File System (PFS) such as Lustre. It will be used to persist global visible files for the system. Node/container-local storage can be used to store files that components do not need. In a cluster, inter-node communication is preferred to go through high-speed network (e.g., 40+Gbps Ethernet).

End-to-end test loop

Run from repo root: /home/kfeng/CLionProjects/ChronoLog_dev/latest/ChronoLog

1. Build (Debug)

tools/deploy/local_single_user_deploy.sh -b -t Debug
  • Build tree: ~/chronolog-build/Debug/
  • For Release/RelWithDebInfo: -t Release / -t RelWithDebInfo
  • Build types are not interchangeable — NDEBUG is defined for Release/RelWithDebInfo and LOG_DEBUG plus any #ifndef NDEBUG blocks are compiled out.

2. Install

tools/deploy/local_single_user_deploy.sh -i -t Debug
  • Install tree: ~/chronolog-install/chronolog/
  • Binaries: ~/chronolog-install/chronolog/bin/{chrono-visor,chrono-keeper,chrono-grapher,chrono-player}
  • Config templates: ~/chronolog-install/chronolog/conf/

Read the full file on GitHub · 245 lines

Changes

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.

  1. 2d ago First seen · 245 lines · 2,955 tokens per session scan A 861fe3ba070b

Subscribe to this mod's changes

chronolog CLAUDE.md is an instructions file published in the GitHub repository grc-iit/chronolog (15 stars, last pushed 2d ago), licensed BSD-2-Clause. It adds 2,955 tokens to every session, about $0.0148 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-07.

DevOps and cloudE2E testingTestingai4hpcdistributed-logdistributed-storagedistributed-systemsevent-streaminghigh-performance-computing
Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,735 tokens