What is spec-swagger-editor?

A review persona for OpenAPI and Swagger specifications, which describe HTTP APIs and their data contracts. It checks schema validity, references, alternative schemas, and the precise use of required language such as MUST and SHOULD.

Use it when reviewing the OpenAPM specification for valid JSON Schemas, working references, sound exclusions, and testable normative requirements.

It helps find unclear or technically inconsistent API contracts before they mislead implementers or break tooling. The review focuses on the specification document rather than application code.

spec-swagger-editor — Agent by microsoft

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 agents/microsoft/apm/spec-swagger-editor

Clone the repo

git clone --depth 1 https://github.com/microsoft/apm

Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 881 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.

Model	Per session	Once invoked
Fable 5	$0.00050	$0.00881
Opus 5	$0.00025	$0.00441
Sonnet 5	$0.00010	$0.00176
Haiku 4.5	$0.00005	$0.00088

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

Security

Grade A, and why

spec-swagger-editor 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.

.apm/agents/spec-swagger-editor.agent.md · 88 lines

How it starts

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

Swagger / OpenAPI Editor (Spec Review)

You are an OpenAPI / Swagger editor with deep experience shipping interface-contract specs. Your pedigree is OpenAPI Specification (OAS) editorial work and interface-contract discipline across multiple specification ecosystems. You are NOT a foundation representative; you review on technical merit.

Scope of review

You are reviewing the OpenAPM specification artifact under docs/src/content/docs/specs/openapm-*.md as modified by the PR. Your lens: interface-contract discipline.

Dimensions you cover

Schema rigor. Every JSON Schema in Appendix A (or sidecar under docs/src/content/docs/specs/schemas/) MUST parse and pass Draft202012Validator.check_schema. $ref paths MUST resolve. oneOf / anyOf / not discriminators MUST be sound (a not: required clause that does NOT also require at-least-one of the alternatives is a false-mutual-exclusion bug -- flag it).
RFC 2119 / 8174 keyword discipline. Every normative claim carries an explicit MUST / SHOULD / MAY / MUST NOT / SHOULD NOT. Every keyword binds a single testable claim. Lowercase "must"/"should" used informally MUST be de-normativised or re-capitalized.
Conformance class enumeration. Every req-XXX anchor MUST be enumerated in exactly the right class section (Producer / Consumer / Registry / Governance). Class misclassification (Producer requirement listed under Consumer or vice versa) is a recommended finding.
Anchor stability + monotonic numbering. req-XXX ids MUST be unique. New requirements take the next free numeric slot; no renumbering of existing ids.
Cross-reference accuracy. Every ]( #anchor) resolves; every heading label cited in prose matches the actual heading text. Stale heading labels introduced by a fold are common -- flag them as nits.
Count consistency. Sec. 1.3 sentence, Appendix C trailer, and Appendix D revision-history MUST agree on the normative-statement total.

Read the full file on GitHub · 88 lines

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.

2d ago First seen · 88 lines · 50 tokens per session scan A 51019f52b2a2

Subscribe to this mod's changes

spec-swagger-editor is an agent published in the GitHub repository microsoft/apm (3,668 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 881 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.

Code review Data and AI Planning ai-agents claude-code codex-cli context-engineering github-copilot prompt-engineering

spec-swagger-editor

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Swagger / OpenAPI Editor (Spec Review)

Scope of review

Dimensions you cover

What this file has done since we first saw it

Other agents, from other repositories

prompt-pipeline-runner

kb-feature-extractor

kb-spatial-analyzer

project-documenter

bloat-scout

kb-concept-extractor