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 AndrewDongminYoo/cc-agents-kit --skill log-itgit clone --depth 1 https://github.com/AndrewDongminYoo/cc-agents-kitWrote 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/andrewdongminyoo/cc-agents-kit/log-it)<a href="https://agentmods.dev/skills/andrewdongminyoo/cc-agents-kit/log-it"><img src="https://agentmods.dev/badge/skills/andrewdongminyoo/cc-agents-kit/log-it/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/andrewdongminyoo/cc-agents-kit/log-it"><img src="https://agentmods.dev/badge/skills/andrewdongminyoo/cc-agents-kit/log-it.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.00058 | $0.01009 |
| Opus 5 | $0.00029 | $0.00504 |
| Sonnet 5 | $0.00012 | $0.00202 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
log-it 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 8d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log It
Overview
A session produces facts with different lifetimes and different readers. Logging them means routing each fact to the store whose reader needs it — never writing one narrative in the most convenient place.
Route each fact by who must see it
| The fact is... | Write to | Its reader |
|---|---|---|
| What the next session in THIS project must know at start (convention, gotcha, state) | project memory ~/.claude/projects/<slug>/memory/, per the memory system prompt |
auto-loaded via MEMORY.md |
| A pattern that holds beyond this project | a cross-project store you keep outside any one repo — or, for agent-behaviour guidance confirmed in 2+ projects, ~/.claude/rules/ |
whatever retrieves precedent for you |
| Unfinished work the next session continues | thin handoff (below) | a SessionStart hook, if you run one |
| Engineering record for humans in the repo | docs/notes/ (global CLAUDE.md convention) |
repo readers |
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.
- 8d ago First seen · 57 lines · 58 tokens per session scan A e8754a10af5e
log-it is a skill published in the GitHub repository AndrewDongminYoo/cc-agents-kit (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,009 once invoked, about $0.0003 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 skills, from other repositories
ucai-patterns
Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems.
memory-curator
Use at session-close when a session captured several new memories, or on-demand, to consolidate, deduplicate, prune, and structure the beads memory store. Triggers on "curate memories", "clean up memories", "memory sweep".
orient
Use when user invokes /orient with a topic keyword, entity type, project name, time qualifier, or combination. Also triggers on "what do we know about X", "remind me about X", "where did we leave off on X". Provides targeted context loading — searches the MCP Memory Server graph, knowledge files, journal entries, and…
capture
Use when user invokes /capture to capture information from the current conversation into a staging file for later reflection and knowledge graph processing. Accepts no arguments (auto-extract), specific facts as text, or filter keywords like "decisions" or "technical". Do NOT use when the user wants to write directly…
session-handoff
A human-invoked utility that writes a grounded session-handoff document (plus a continuation pointer memory) so a fresh agent can resume in-progress work. Not auto-invoked; a human runs it deliberately.
furl
How the Furl context-compression plugin works in Claude Code and Codex — the furlcompress / furlretrieve / furlstats / furlpurge / furlsearch / furllist MCP tools, the > retrieval flow, and Claude Code's optional automatic hooks. Use when the user asks what Furl is doing, how to compress or retrieve content, why…