openapi-workflow

A workflow for changing an OpenAPI contract and regenerating the client code that comes from it. OpenAPI is a machine-readable description of an API.

In plain words
What is it for?
Use it when changing Agent or Admin API definitions, regenerating their bindings and clients, and compiling or building the affected projects.
Why use it?
It reduces mismatches between the API specification and generated Go, Java, and TypeScript clients.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/chirino/memory-service/openapi-workflow
Any agent
npx skills add chirino/memory-service --skill openapi-workflow
Clone the repo
git clone --depth 1 https://github.com/chirino/memory-service

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 327 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00024 $0.00327
Opus 5 $0.00012 $0.00163
Sonnet 5 $0.00005 $0.00065
Haiku 4.5 $0.00002 $0.00033

Measured 2d ago against content hash b89f9dbacdcc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openapi-workflow 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 2d 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/openapi-workflow/SKILL.md · 35 lines

What it actually says

OpenAPI Change Workflow

  1. Edit the spec: Agent API changes use contracts/openapi/openapi.yml; Admin API changes use contracts/openapi/openapi-admin.yml.

  2. Regenerate Go bindings:

    # Agent API + client
    go run github.com/oapi-codegen/oapi-codegen/v2/cmd/oapi-codegen --config=internal/generated/api/cfg.yaml contracts/openapi/openapi.yml
    go run github.com/oapi-codegen/oapi-codegen/v2/cmd/oapi-codegen --config=internal/generated/apiclient/cfg.yaml contracts/openapi/openapi.yml
    
    # Admin API
    go run github.com/oapi-codegen/oapi-codegen/v2/cmd/oapi-codegen --config=internal/generated/admin/cfg.yaml contracts/openapi/openapi-admin.yml
    
  3. Regenerate Java client:

    ./java/mvnw -f java/pom.xml -pl quarkus/memory-service-rest-quarkus clean compile -am
    
  4. Regenerate TypeScript client:

    cd frontends/chat-frontend && npm run generate
    
  5. Verify:

    ./java/mvnw -f java/pom.xml compile
    cd frontends/chat-frontend && npm run lint && npm run build
    
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. 2d ago First seen · 35 lines · 24 tokens per session scan A b89f9dbacdcc

Subscribe to this mod's changes

openapi-workflow is a skill published in the GitHub repository chirino/memory-service (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 24 tokens to every session and 327 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens