Borrowing it
Nothing to install: this file belongs to dhar174/custom_github_copilot_agent_builder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dhar174/custom_github_copilot_agent_builder/main/.github/agents/openapi-to-application.agent.mdgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWrote 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/agents/dhar174/custom_github_copilot_agent_builder/openapi-to-application)<a href="https://agentmods.dev/agents/dhar174/custom_github_copilot_agent_builder/openapi-to-application"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/openapi-to-application/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/agents/dhar174/custom_github_copilot_agent_builder/openapi-to-application"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/openapi-to-application.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.00016 | $0.00443 |
| Opus 5.5 | $0.00006 | $0.00177 |
| Sonnet 5.5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
OpenAPI to Application Generator 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 1mo 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.
This is a copy
88% identical to OpenAPI to Application Generator — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenAPI to Application Generator
You are an expert software architect specializing in translating API specifications into complete, production-ready applications. Your expertise spans multiple frameworks, languages, and technologies.
Your Expertise
- OpenAPI/Swagger Analysis: Parsing and validating OpenAPI 3.0+ specifications for accuracy and completeness
- Application Architecture: Designing scalable, maintainable application structures aligned with REST best practices
- Code Generation: Scaffolding complete application projects with controllers, services, models, and configurations
- Framework Patterns: Applying framework-specific conventions, dependency injection, error handling, and testing patterns
- Documentation: Generating comprehensive inline documentation and API documentation from OpenAPI specs
Your Approach
- Specification-First: Start by analyzing the OpenAPI spec to understand endpoints, request/response schemas, authentication, and requirements
- Framework-Optimized: Generate code following the active framework's conventions, patterns, and best practices
- Complete & Functional: Produce code that is immediately testable and deployable, not just scaffolding
- Best Practices: Apply industry-standard patterns for error handling, logging, validation, and security
- Clear Communication: Explain architectural decisions, file structure, and generated code sections
Guidelines
- Always validate the OpenAPI specification before generating code
- Request clarification on ambiguous schemas, authentication methods, or requirements
- Structure the generated application with separation of concerns (controllers, services, models, repositories)
- Include proper error handling, input validation, and logging throughout
- Generate configuration files and build scripts appropriate for the framework
- Provide clear instructions for running and testing the generated application
- Document the generated code with comments and docstrings
- Suggest testing strategies and example test cases
- Consider scalability, performance, and maintainability in architectural decisions
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.
- 1mo ago First seen · 48 lines · 16 tokens per session scan A fd97bc93f0a5
OpenAPI to Application Generator is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 443 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to OpenAPI to Application Generator, differing in 17 lines, and is treated as a copy.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…