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 commands/indranildchandra/claude-local-starter/log-contextgit clone --depth 1 https://github.com/indranildchandra/claude-local-starterWrote 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/commands/indranildchandra/claude-local-starter/log-context)<a href="https://agentmods.dev/commands/indranildchandra/claude-local-starter/log-context"><img src="https://agentmods.dev/badge/commands/indranildchandra/claude-local-starter/log-context.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.00030 | $0.00368 |
| Opus 5 | $0.00015 | $0.00184 |
| Sonnet 5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
log-context 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.
What it actually says
You are writing a pre-compact context snapshot. Follow these steps exactly.
Step 1 — Load the format
Read aidlc-tracking skill formats.md for the pre-compact snapshot entry format before writing anything.
Step 2 — Gather session context
Reflect on the current conversation and identify:
- Working on: What is the current task or goal?
- Completed this session: What has been finished since the session started or since the last snapshot?
- Key decisions: What significant decisions were made and why?
- Files changed: Which files were created, modified, or deleted?
- Open / in-progress: What is unfinished or blocked?
- Resume from: The exact state a fresh session would need to pick up — specific file, function, step, or error being worked on. Be precise enough that no context is required from the conversation history.
Step 3 — Write to tasks/tracker.md
Prepend the pre-compact snapshot entry to tasks/tracker.md so the newest entry is at the top.
If tasks/tracker.md does not exist: create it with the header from aidlc-tracking formats.md, then write the entry below the header.
If tasks/tracker.md already exists: insert the new entry immediately after the file header (first 3 lines), pushing all prior entries down. Do NOT append to the end of the file.
Step 4 — Confirm
Tell the user: "Context logged to tasks/tracker.md — safe to /compact." Show the Resume from line so the user can verify it captures the current state.
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 · 33 lines · 30 tokens per session scan A bafa10c315c9
log-context is a command published in the GitHub repository indranildchandra/claude-local-starter (13 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 368 once invoked, about $0.0002 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-30.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.