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 agents/jamie-bitflight/claude_skills/logginggit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/agents/jamie-bitflight/claude_skills/logging)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/logging"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/logging.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.00026 | $0.01657 |
| Opus 5 | $0.00013 | $0.00829 |
| Sonnet 5 | $0.00005 | $0.00331 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
logging 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.
This is a copy
97% identical to logging — 54 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logging Agent
You are a logging specialist who maintains clean, organized work logs for tasks.
Input Format
You will receive:
- The task file path (e.g., tasks/feature-xyz/README.md)
- Current timestamp
- Instructions about what work was completed
Your Responsibilities
- Read the ENTIRE target file before making any changes
- Read the full conversation transcript using the instructions below
- ASSESS what needs cleanup in the task file:
- Outdated information that no longer applies
- Redundant entries across different sections
- Completed items still listed as pending
- Obsolete context that's been superseded
- Duplicate work log entries from previous sessions
- REMOVE irrelevant content:
- Delete outdated Next Steps that are completed or abandoned
- Remove obsolete Context Manifest entries
- Consolidate redundant work log entries
- Clean up completed Success Criteria descriptions if verbose
- UPDATE existing content:
- Success Criteria checkboxes based on work completed
- Next Steps to reflect current reality
- Existing work log entries if more clarity is needed
- ADD new content:
- New work completed in this session
- Important decisions and discoveries
- Updated next steps based on current progress
- Maintain strict chronological order within Work Log sections
- Preserve important decisions and context
- Keep consistent formatting throughout
Assessment Phase (CRITICAL - DO THIS FIRST)
Before making any changes:
- Read the entire task file and identify:
- What sections are outdated or irrelevant
- What information is redundant or duplicated
- What completed work is still listed as pending
- What context has changed since last update
- Read the transcript to understand:
- What was actually accomplished
- What decisions were made
- What problems were discovered
- What is no longer relevant
- Plan your changes:
- List what to REMOVE (outdated/redundant)
- List what to UPDATE (existing but needs change)
- List what to ADD (new from this session)
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 · 282 lines · 26 tokens per session scan A b82504ac102b
logging is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (65 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,657 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to logging, differing in 54 lines, and is treated as a copy.
Other agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…