Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/muyen/vibe-to-prodnpx agentmods add skills/muyen/vibe-to-prod/openapi-workflowWrote 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/muyen/vibe-to-prod/openapi-workflow)<a href="https://agentmods.dev/skills/muyen/vibe-to-prod/openapi-workflow"><img src="https://agentmods.dev/badge/skills/muyen/vibe-to-prod/openapi-workflow/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.
<a href="https://agentmods.dev/skills/muyen/vibe-to-prod/openapi-workflow"><img src="https://agentmods.dev/badge/skills/muyen/vibe-to-prod/openapi-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00528 |
| Opus 5.5 | $0.00012 | $0.00211 |
| Sonnet 5.5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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 12d 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.
What it actually says
OpenAPI Workflow Skill
Automatically runs the OpenAPI workflow when spec files are modified.
When to Activate
This skill should activate when:
- Files in
backend/api/*.yamlare modified - New endpoints are added to OpenAPI spec
- Request/response schemas are changed
- User asks to add/modify API endpoints
OpenAPI Spec Location
| Type | Path | Purpose |
|---|---|---|
| API Spec | backend/api/openapi.yaml |
Public API definition |
Workflow Steps
1. Validate Spec
python3 scripts/openapi_workflow.py --validate
2. Generate Code (All Platforms)
python3 scripts/openapi_workflow.py --codegen
This generates:
- Backend (Go):
backend/internal/generated/ - iOS (Swift):
mobile/ios/App/Generated/ - Android (Kotlin):
mobile/android/app/src/main/java/.../generated/ - Web (TypeScript):
web/src/generated/
3. Build Verification
python3 scripts/openapi_workflow.py --build
4. Full Workflow (All Steps)
python3 scripts/openapi_workflow.py --full
Critical Rules
| Rule | Why |
|---|---|
| Define response schemas properly | Inline schemas don't generate reusable types |
| Use plural file names | REST convention: users.yaml not user.yaml |
| Always regenerate after spec changes | Generated code must match spec |
| Verify ALL platforms build | API changes affect backend + iOS + Android + web |
Process
- Detect OpenAPI spec was modified
- Run validation to catch syntax/semantic errors
- Regenerate code for all platforms
- Run build verification
- Report any failures
Output Format
## OpenAPI Workflow Results
**Spec Modified**: [file path]
**Validation**: ✅ Passed / ❌ Failed
**Code Generation**: ✅ All platforms / ❌ Failed for [platform]
**Build Verification**: ✅ All platforms / ❌ Failed for [platform]
[Details of any failures]
Reference
- Script:
scripts/openapi_workflow.py - Spec:
backend/api/openapi.yaml
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.
- 12d ago First seen · 86 lines · 30 tokens per session scan A 0bffe780a6c2
openapi-workflow is a skill published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 528 once invoked, about $0.0001 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-10-04.
Other skills, from other repositories
django-docs
Use this skill whenever the user asks about Django, Python web development, ORM models, migrations, views, templates, forms, admin, authentication, middleware, testing, caching, security, REST APIs, or deployment. Covers Django 6.0 including the model layer (fields, QuerySets, relationships, migrations, managers…
api-contract-first-development
Define API contracts before implementation to reduce integration errors and preserve backward compatibility. Use when designing or updating REST, GraphQL, or event-driven interfaces between UI and backend services.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
team-polish
Orchestrate the polish team — performance-analyst, technical-artist, sound-designer, qa-tester — to optimize and harden a feature or area.
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.