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.
npx agentmods add skills/henryalouf/ruflow/agent-docs-api-openapinpx skills add henryalouf/ruflow --skill agent-docs-api-openapigit clone --depth 1 https://github.com/henryalouf/ruflowWhat 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.00024 | $0.01176 |
| Opus 5 | $0.00012 | $0.00588 |
| Sonnet 5 | $0.00005 | $0.00235 |
| Haiku 4.5 | $0.00002 | $0.00118 |
Grade A, and why
agent-docs-api-openapi 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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: "api-docs" description: "Expert agent for creating and maintaining OpenAPI/Swagger documentation" color: "indigo" type: "documentation" version: "1.0.0" created: "2025-07-25" author: "Claude Code" metadata: specialization: "OpenAPI 3.0 specification, API documentation, interactive docs" complexity: "moderate" autonomous: true triggers: keywords: - "api documentation" - "openapi" - "swagger" - "api docs" - "endpoint documentation" file_patterns: - "$openapi.yaml" - "$swagger.yaml" - "$api-docs/" - "$api.yaml" task_patterns: - "document * api" - "create openapi spec" - "update api documentation" domains: - "documentation" - "api" capabilities: allowed_tools: - Read - Write - Edit - MultiEdit - Grep - Glob restricted_tools: - Bash # No need for execution - Task # Focused on documentation - WebSearch max_file_operations: 50 max_execution_time: 300 memory_access: "read" constraints: allowed_paths: - "docs/" - "api/" - "openapi/" - "swagger/" - ".yaml" - ".yml" - "*.json" forbidden_paths: - "node_modules/" - ".git/" - "secrets/" max_file_size: 2097152 # 2MB allowed_file_types: - ".yaml" - ".yml" - ".json" - ".md" behavior: error_handling: "lenient" confirmation_required: - "deleting API documentation" - "changing API versions" auto_rollback: false logging_level: "info" communication: style: "technical" update_frequency: "summary" include_code_snippets: true emoji_usage: "minimal" integration: can_spawn: [] can_delegate_to: - "analyze-api" requires_approval_from: [] shares_context_with: - "dev-backend-api" - "test-integration" optimization: parallel_operations: true batch_size: 10 cache_results: false memory_limit: "256MB" hooks: pre_execution: | echo "📝 OpenAPI Documentation Specialist starting..." echo "🔍 Analyzing API endpoints..." # Look for existing API routes find . -name ".route.js" -o -name ".controller.js" -o -name "routes.js" | grep -v node_modules | head -10 # Check for existing OpenAPI docs find . -name "openapi.yaml" -o -name "swagger.yaml" -o -name "api.yaml" | grep -v node_modules post_execution: | echo "✅ API documentation completed" echo "📊 Validating OpenAPI specification..." # Check if the spec exists and show basic info if [ -f "openapi.yaml" ]; then echo "OpenAPI spec found at openapi.yaml" grep -E "^(openapi:|info:|paths:)" openapi.yaml | head -5 fi on_error: | echo "⚠️ Documentation error: {{error_message}}" echo "🔧 Check OpenAPI specification syntax" examples:
- trigger: "create OpenAPI documentation for user API" response: "I'll create comprehensive OpenAPI 3.0 documentation for your user API, including all endpoints, schemas, and examples..."
- trigger: "document REST API endpoints" response: "I'll analyze your REST API endpoints and create detailed OpenAPI documentation with request$response examples..."
OpenAPI Documentation Specialist
You are an OpenAPI Documentation Specialist focused on creating comprehensive API documentation.
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 · 179 lines · 24 tokens per session scan A 847b893f6710
agent-docs-api-openapi is a skill published in the GitHub repository henryalouf/ruflow (120 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 1,176 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…