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 skills/chirino/memory-service/operationevent-loggingnpx skills add chirino/memory-service --skill operationevent-logginggit clone --depth 1 https://github.com/chirino/memory-serviceWrote 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/chirino/memory-service/operationevent-logging)<a href="https://agentmods.dev/skills/chirino/memory-service/operationevent-logging"><img src="https://agentmods.dev/badge/skills/chirino/memory-service/operationevent-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.1 | $0.00057 | $0.01475 |
| Opus 5 | $0.00028 | $0.00737 |
| Sonnet 5 | $0.00011 | $0.00295 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
operationevent-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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operation Event Logging
Use internal/operationevent for canonical operation records. Preserve API contracts, request-ID behavior, audit records, and independently scoped diagnostic logs.
Workflow
- Identify the operation boundary and its stable name:
- REST:
http METHOD /route/{parameter}fromgin.Context.FullPath(); use<unmatched>when absent. - gRPC:
grpc /package.Service/Methodfrom the full method. - Jobs: an allowlisted
job.*name.
- REST:
- Create and attach the event at the outer boundary after request-ID propagation and before rate limiting, authentication, recovery, and application work.
- Enrich only through typed setters. Set identity and resource IDs after they are validated or resolved. Do not add an arbitrary properties map.
- REST wrappers with generic path names such as
idmust set the resource-specific field explicitly. - gRPC request-derived IDs must not be applied to authentication, rate-limit, or syntactic-validation rejections; explicit handler enrichment takes precedence.
- Map generic gRPC protobuf fields such as
idby full RPC method. Never infer their resource type globally. - gRPC datastore transaction helpers mark request resources validated. A handler that starts authorized, validated work without those helpers must call
security.MarkGRPCOperationResourcesValidatedbefore that work.
- REST wrappers with generic path names such as
- Emit no more than one
startrecord, and only for streams or substantial background work. Emit exactly one terminal record at every boundary. - Enrich errors only when they determine the terminal result. Do not enrich successful fallback, expected absence, ignored best-effort work, or an eventually successful in-process retry.
- Run focused race tests, then the affected project verification.
Terminal results
Use the shared mapping in internal/operationevent:
| Outcome | Result |
|---|---|
| HTTP 2xx/3xx or gRPC OK | success |
| HTTP 400/422 or InvalidArgument/OutOfRange | invalid |
| HTTP 401 or Unauthenticated | unauthenticated |
| HTTP 403 or PermissionDenied | forbidden |
| HTTP 404 or NotFound | not_found |
| HTTP 409 or AlreadyExists/Aborted/FailedPrecondition | conflict |
| HTTP 429 or ResourceExhausted | rate_limited |
| Deadline expiry | timed_out |
| Client or context cancellation | canceled |
| Other caller rejection | rejected |
| HTTP 5xx or Internal/Unavailable/DataLoss | failed |
| Failed task attempt successfully returned to its retry queue | retrying |
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.
- 5d ago First seen · 96 lines · 57 tokens per session scan A 9b9d9ff5bb33
operationevent-logging is a skill published in the GitHub repository chirino/memory-service (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,475 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…