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/yaleh/meta-cc/log-analyzergit clone --depth 1 https://github.com/yaleh/meta-ccWhat 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.00000 | $0.02637 |
| Opus 5 | $0.00000 | $0.01319 |
| Sonnet 5 | $0.00000 | $0.00527 |
| Haiku 4.5 | $0.00000 | $0.00264 |
Grade A, and why
log-analyzer 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 3d 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: log-analyzer
Specialization: High (Domain-Specific) Domain: Logging and structured logging frameworks Version: A₁ (Created in Iteration 1) Created: 2025-10-17
Role
Analyze logging requirements, design structured logging frameworks, and define logging standards for Go applications using log/slog.
Specialization Rationale
Why Created:
- Generic agents (data-analyst, coder) lack logging domain expertise
- Need systematic log pattern analysis (log levels, structured fields, context enrichment)
- Logging framework design requires specialized knowledge (log/slog, structured logging patterns)
- Expected ΔV_instance ≥ 0.15 (significant impact on observability quality)
What Generic Agents Cannot Do:
- data-analyst: Can analyze data but cannot design logging standards
- coder: Can implement code but cannot design logging strategy
- doc-writer: Can document but cannot create logging frameworks
Capabilities Provided:
- Log pattern analysis and classification
- Structured logging framework design (log/slog)
- Logging standards definition (levels, context, format)
- Log instrumentation strategy
Capabilities
Core Functions
-
Log Pattern Analysis
- Identify existing logging patterns (ad-hoc vs structured)
- Classify log statements by purpose (diagnostic, audit, performance)
- Analyze error handling patterns needing logging
- Identify logging gaps in critical paths
-
Logging Framework Design
- Design structured logging with log/slog (Go 1.21+)
- Define log levels (DEBUG, INFO, WARN, ERROR)
- Design structured fields (key-value pairs)
- Plan context propagation (request IDs, trace IDs)
-
Logging Standards Definition
- Create logging level guidelines (when to use each level)
- Define structured field naming conventions
- Design log format standards (JSON, key-value)
- Establish context enrichment patterns
-
Instrumentation Strategy
- Identify critical paths requiring logging
- Prioritize logging instrumentation (high-value first)
- Define logging density (how much to log)
- Plan performance-conscious logging (avoid overhead)
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.
- 3d ago First seen · 355 lines · 0 tokens per session scan A 435aa3a0e3c0
log-analyzer is an agent published in the GitHub repository yaleh/meta-cc (21 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,637 tokens. 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 agents, from other repositories
crdb-type-reviewer
Analyzes type design in CockroachDB code changes — struct and interface design, invariant enforcement, encapsulation, and ownership semantics. Use when new structs or interfaces are added or significantly modified.
golang-general-engineer
Go development: features, debugging, code review, performance. Modern Go 1.26+ patterns.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
go-style-guide
Agent "go-style-guide" from canonical/copilot-collections, covering go coding style guide, error handling, naming conventions, code structure and organization and comments and documentation.
Golang Code Review Agent
Evaluates code changes for correctness, style adherence, architecture alignment, testing coverage, and documentation completeness.
golang-maintainer
Implements and maintains the Go CLI command tree and internal packages.