memory-service: Skill for Codex

.skills/operationevent-logging/SKILL.md

operationevent-logging is a skill for Codex from chirino/memory-service. It costs 57 tokens per session (1,475 once invoked), scanned A, original, Apache-2.0.

A workflow for recording operational events in a backend service, including requests, errors, background jobs, indexes, and streaming connections.

In plain words
What is it for?
Use it when adding or reviewing logging at REST or gRPC endpoints, workers, maintenance jobs, indexers, SSE streams, and related backend boundaries.
Why use it?
It keeps operation records, request IDs, audit information, and diagnostic logs consistent across different parts of the service.

Skill for Codex

Written for Codex: agents/openai.yaml present.

This is chirino/memory-service's own configuration. It tells Codex how to work on memory-service itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything memory-service configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is go test -race ./internal/operationevent ./internal/security ./internal/service ./internal/grpc ./internal/cmd/serve -count=1.

Reuse

Borrowing it

Nothing to install: this file belongs to chirino/memory-service. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/chirino/memory-service/main/.skills/operationevent-logging/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/chirino/memory-service

Made for: Codex.

Wrote 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.

agentmods badge for operationevent-logging

README.md
[![agentmods](https://agentmods.dev/badge/skills/chirino/memory-service/operationevent-logging/github.svg)](https://agentmods.dev/skills/chirino/memory-service/operationevent-logging)
Your own site
<a href="https://agentmods.dev/skills/chirino/memory-service/operationevent-logging"><img src="https://agentmods.dev/badge/skills/chirino/memory-service/operationevent-logging/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.

agentmods 80×15 button for operationevent-logging

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,475 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.01475
Opus 5.5 $0.00023 $0.00590
Sonnet 5.5 $0.00011 $0.00295
Haiku 4.5 $0.00006 $0.00147

Measured 2mo ago against content hash 9b9d9ff5bb33, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.skills/operationevent-logging/SKILL.md · 96 lines

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

  1. Identify the operation boundary and its stable name:
    • REST: http METHOD /route/{parameter} from gin.Context.FullPath(); use <unmatched> when absent.
    • gRPC: grpc /package.Service/Method from the full method.
    • Jobs: an allowlisted job.* name.
  2. Create and attach the event at the outer boundary after request-ID propagation and before rate limiting, authentication, recovery, and application work.
  3. 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 id must 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 id by 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.MarkGRPCOperationResourcesValidated before that work.
  4. Emit no more than one start record, and only for streams or substantial background work. Emit exactly one terminal record at every boundary.
  5. 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.
  6. 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

Read the full file on GitHub · 96 lines

Files

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.

Changes

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.

  1. 2mo ago First seen · 96 lines · 57 tokens per session scan A 9b9d9ff5bb33

Subscribe to this mod's changes

operationevent-logging is a skill published in the GitHub repository chirino/memory-service (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 1,475 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.

Related

Other skills, from other repositories

mem0-oss-to-platform

Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…

mem0ai/mem0 · 217 tokens

agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…

ag-ui-protocol/ag-ui · 162 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

dev-runtime

How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…

langwatch/langwatch · 172 tokens

api-design

Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…

ericrisco/rsc-harness · 105 tokens