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/genocs/genocs-library/webapi-buildernpx skills add Genocs/genocs-library --skill webapi-buildergit clone --depth 1 https://github.com/Genocs/genocs-libraryWhat 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.00021 | $0.00194 |
| Opus 5 | $0.00010 | $0.00097 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
webapi-builder 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.
What it actually says
Introduction
Use this skill to implement Web API services to implement microservices-based backend systems. The APIs should follow the best practices and conventions for RESTful API design, including:
- Use of HTTP methods (GET, POST, PUT, DELETE) appropriately.
- Use CQRS pattern to separate read and write operations for better scalability and maintainability.
- Publish messages to a message broker (e.g., RabbitMQ, Azure Service Bus) for asynchronous processing and decoupling of services.
- Use OpenAPI/Swagger for API documentation and testing.
- Use Genocs Library official documentation to scaffold web APIs or Worker services, which provides a set of tools and templates to help you get started quickly. Full documentation for the Genocs Library can be found at Genocs 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 · 22 lines · 21 tokens per session scan A 7d3a5cce8136
webapi-builder is a skill published in the GitHub repository Genocs/genocs-library (4 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 194 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-31.
Other skills, from other repositories
code-review-architecture
Architecture-focused code review covering hexagonal boundary violations, DDD anti-patterns, CQRS misuse, and microservices coupling issues. Applied in addition to the language-specific review skill when architecture markers are detected. Invoked when reviewing hexagonal architectures, DDD patterns, or microservices…
architecture-patterns
Software architecture patterns and best practices.
enterprise-architecture-patterns
Complete guide for enterprise architecture patterns including domain-driven design, event sourcing, CQRS, saga patterns, API gateway, service mesh, and scalability.
ddd
领域驱动设计（DDD）建模与架构指导。用于创建领域模型、设计限界上下文、实现聚合根、实体、值对象、领域服务和领域事件。支持战略设计（上下文映射、子域划分）和战术设计（聚合、仓储、工厂模式）。当用户需要进行领域建模、微服务划分、复杂业务逻辑设计时使用。.
titan
Heavy-duty architectural specialist building indestructible backend systems. API design, microservices, DDD, and database-backed services.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…