Borrowing it
Nothing to install: this file belongs to ctxpipe-ai/ctxpipe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ctxpipe-ai/ctxpipe/main/.agents/skills/review-logging-patterns/SKILL.mdgit clone --depth 1 https://github.com/ctxpipe-ai/ctxpipeWrote 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/ctxpipe-ai/ctxpipe/review-logging-patterns)<a href="https://agentmods.dev/skills/ctxpipe-ai/ctxpipe/review-logging-patterns"><img src="https://agentmods.dev/badge/skills/ctxpipe-ai/ctxpipe/review-logging-patterns/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/ctxpipe-ai/ctxpipe/review-logging-patterns"><img src="https://agentmods.dev/badge/skills/ctxpipe-ai/ctxpipe/review-logging-patterns.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.00053 | $0.01206 |
| Opus 5.5 | $0.00021 | $0.00482 |
| Sonnet 5.5 | $0.00011 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
review-logging-patterns 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 28d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review logging patterns
Backend and codesearch log with evlog on Hono (Bun). The UI browser logger is evlog/client. One wide event per request or job.
When to use
- Adding a log in
apps/backendorapps/codesearch - Replacing
console.*with evlog - Reviewing a wide event, a structured error, or the drain
App-local rules: apps/backend/AGENTS.md (Logging), apps/codesearch/AGENTS.md (Logging).
Which logger
| Context | Call |
|---|---|
| Hono handler or middleware | getLogger() from src/observability/logger.ts (same logger as c.var.log) |
Workflow or graph node inside withLogger |
getLogger() |
| Domain helper, DB hook, or bootstrap with no request | log from the same module (log.info / log.error emit immediately) |
| Long job that must flush before return | createLogger + withLogger; codesearch index phases call flushWorkflowLog() |
| Browser | setIdentity / clearIdentity from evlog/client in useAuthEvlogIdentity.ts |
getLogger() throws when neither Hono context nor AsyncLocalStorage has a logger. A script that skips server.ts calls initEvlog() once at entry.
Hono setup
Both apps register one evlog() middleware from evlog/hono.
- Backend:
apps/backend/src/app/app.tscallsevlog()with no drain. The drain isinitLogger. - Codesearch:
apps/codesearch/src/app/app.tspassescreateEvlogDrain()and runsapplyCodesearchLogContractinenrich.
Drain
Backend initLogger({ silent, redact, drain }) in logger.ts is the only backend drain. The drain calls applyLogContract, writes JSON to stdout in production, and sends OTLP with createOTLPDrain from evlog/otlp (5 s timeout, no retry). flushEvlog() awaits in-flight sends.
Codesearch wraps createOTLPDrain in createDrainPipeline (batch 50 / 5 s, 3 retries, then onDropped). flushEvlog() calls drain.flush().
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 28d ago Changed · -686 lines · -53 tokens per session 85f6bd945be6
- 1mo ago First seen · 761 lines · 106 tokens per session scan A f2318551e350
review-logging-patterns is a skill published in the GitHub repository ctxpipe-ai/ctxpipe (27 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,206 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
qa-review
Validate that implemented code fully satisfies Story acceptance criteria, respects rules, and introduces no regressions. This is the hard quality gate — no pass means no delivery. Activate after implementation is complete.
consistency-check
Detect inconsistencies across related artefacts and governance constraints. Activate after story generation, after plan preparation, before implementation, or after remediation attempts. Reports issues — does not fix them.
tendril-review
Comprehensive post-change review of all modified files. Checks for code smells, cleanup opportunities, unnecessary legacy support, missing tests, broken tests, and obsolete tests. Use after a big change to leave the codebase in better health.
code-review
Performs multi-dimensional code review covering security, quality, spec compliance, and maintainability. Used when reviewing completed implementations or before merging changes.
maxsim-simplify
Reviews changed code for reuse opportunities, quality issues, and efficiency improvements, then fixes actionable items. Used after implementing features or when code feels over-engineered.
improve-codebase-architecture
Surface deepening refactors that turn shallow modules into deep ones, informed by CONTEXT.md and docs/adr/. Use when the user asks to improve architecture, find refactor candidates, raise testability, or make a codebase more agent-navigable. Skip for single localized fixes.