agentmods.dev

change-server-api

change-server-api is a skill for Codex from SII-Holos/synergy. It costs 62 tokens per session (524 once invoked), scanned A, original, MIT.

A workflow for changing Synergy’s internal HTTP APIs, including routes, data formats, generated SDK methods, and frontend calls. It covers both ordinary request-and-response APIs and streaming or file-transfer boundaries.

In plain words
What is it for?
Use it to add or modify server routes, OpenAPI descriptions, request or response schemas, SDK methods, frontend API calls, snapshots, uploads, downloads, or streams.
Why use it?
It helps keep the server, generated client code, and frontend in agreement when an API changes. It also reduces mistakes around validation, permissions, scope, errors, and state updates.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Not installable on its own: it runs a file from its repository that does not travel with it. Clone the repository, or install whatever ships that file. The line is ./script/generate.ts.

not rated 548 today A scan 62 tokens original MIT
View the source file SII-Holos/synergy synergy.holosai.io
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

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 change-server-api

README.md
[![agentmods](https://agentmods.dev/badge/skills/sii-holos/synergy/change-server-api.svg)](https://agentmods.dev/skills/sii-holos/synergy/change-server-api)
Your own site
<a href="https://agentmods.dev/skills/sii-holos/synergy/change-server-api"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/change-server-api.svg" alt="Measured on agentmods" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 524 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.1 $0.00062 $0.00524
Opus 5 $0.00031 $0.00262
Sonnet 5 $0.00012 $0.00105
Haiku 4.5 $0.00006 $0.00052

Measured 6d ago against content hash a9fd6ec224b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

change-server-api 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 6d 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.

.synergy/skill/change-server-api/SKILL.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Change a Server API

Trace the Contract

  1. Inspect the nearest route, its owning domain service, route tests, generated SDK method, and every first-party consumer.
  2. Decide whether the route is global, home-scoped, project-scoped, session-owned, or workspace-owned. Preserve Scope/directory resolution and authorization.
  3. Decide whether the behavior is request/response state, a sequenced state event, or a streaming transport. Do not force WebSocket, SSE, WebRTC, file/blob, or external URL behavior into an ordinary SDK call.

Implement

  1. Validate path, query, form, and body input with precise Zod schemas.
  2. Add describeRoute metadata, stable operationId, response schemas, and structured error responses. Add .meta({ ref: "TypeName" }) for reusable API-visible schemas.
  3. Keep business logic in the owning domain rather than the route handler.
  4. For state changes, persist first and publish the established event shape so frontend state can reconcile without per-event refetches.
  5. Preserve scoped snapshot watermark headers where middleware supplies them. Do not claim Web snapshot gating that the client does not implement.
  6. Regenerate contracts from the repository root:
./script/generate.ts
  1. Replace or add frontend calls through createSynergyClient() / the generated SDK. Preserve auth, Scope/directory parameters, errors, and asset URL formats.

Verify

  1. Test validation, success, domain error, Scope ownership, and event behavior at the narrowest route/domain level.
  2. Typecheck the runtime, SDK, and affected client.
  3. Run the affected frontend context/component test when response identity or event reconciliation changes.
  4. Inspect the generated diff; do not hand-edit generated SDK files.
  5. Run bun run quality:quick after focused checks.

Update Frontend data sync when snapshot/event/replay semantics change, and update API/help/product docs when the route is a public or user-facing contract.

Read the full file on GitHub · 42 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. 6d ago First seen · 42 lines · 62 tokens per session scan A a9fd6ec224b2

Subscribe to this mod's changes

change-server-api is a skill published in the GitHub repository SII-Holos/synergy (548 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 524 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.

Backend and APIs
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

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

microsoft/vscode · 72 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

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…

vercel/next.js · 95 tokens