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/luizjhonata/chlog/claude-mdgit clone --depth 1 https://github.com/luizjhonata/chlogWrote 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/luizjhonata/chlog/claude-md)<a href="https://agentmods.dev/instructions/luizjhonata/chlog/claude-md"><img src="https://agentmods.dev/badge/instructions/luizjhonata/chlog/claude-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.01118 | $0.01118 |
| Opus 5 | $0.00559 | $0.00559 |
| Sonnet 5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
chlog 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 5d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
What This Project Does
chlog is a fragment-based changelog CLI. Each PR creates a YAML fragment in .changes/unreleased/; at release time, fragments are compiled into CHANGELOG.md. Designed to eliminate merge conflicts on CHANGELOG.md in multi-developer environments.
It is a local filesystem tool — no Git, no APIs, no provider integration. Works in any repo.
Build & Development Commands
make build # compile binary to bin/chlog
make debug # compile with debug symbols
make run # go run .
make install # build + copy to ~/.local/bin
make lint, make test, and make sast require the shared pipelines repo cloned at ~/Development/github.com/rios0rios0/pipelines. Without it, use the commands below directly.
Lint (CI uses golangci-lint v2 with external config — local v1 misses issues):
~/go/bin/golangci-lint run --config ~/Development/github.com/rios0rios0/pipelines/global/scripts/languages/golang/golangci-lint/.golangci.yml ./...
Tests:
go test -tags unit -count=1 -v ./...
go test -tags unit -run "TestName" ./cmd/ # single test
go test -tags unit -run "TestName" ./internal/ # single test
Architecture
Flat, idiomatic Go. No CQRS, no DI container.
main.go— entry point, version injection via ldflagscmd/— Cobra commands with business logic inlineinternal/— shared types (Config, Change) with Go-native import protection
Key External Libraries
github.com/spf13/cobra— CLI frameworkgithub.com/Masterminds/semver/v3— semantic versioninggopkg.in/yaml.v3— YAML parsinggithub.com/stretchr/testify— test assertions (test only)
Testing Conventions
- Build tag:
//go:build uniton all test files - BDD structure:
// given,// when,// then - Test names:
t.Run("should ... when ...", ...) - Do NOT use
t.Parallel()incmd/tests — they useos.Chdirwhich is process-global t.Parallel()is used ininternal/testst.TempDir()for filesystem isolation- testify/assert + testify/require
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.
- 5d ago First seen · 112 lines · 1,118 tokens per session scan A 163ac91b3d16
chlog CLAUDE.md is an instructions file published in the GitHub repository luizjhonata/chlog (5 stars, last pushed 11d ago), licensed MIT. It adds 1,118 tokens to every session, about $0.0056 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
kanban-md AGENTS.md
Instructions for antopolskiy/kanban-md, covering guidelines, releasing, ci verification (required), release notes and new: feature name (by @contributor).
google-play-cli AGENTS.md
Instructions for PollyGlot/google-play-cli, covering agents.md : gplay, glossary, commandes, vérifier and les pièges de ce repo.
firefly copilot-instructions.md
Copilot instructions for yehezkieldio/firefly, covering development instructions, firefly, 1. technology stack, 2. coding standards and 3. coding patterns.
runecho CLAUDE.md
Claude Code instructions for inth3shadows/runecho, covering runecho workflow, release tags and git hooks — there are five, from two different installers.
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
chatgpt-cli CLAUDE.md
Claude Code instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.