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.
git clone --depth 1 https://github.com/TheLobbi/claudeWrote 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/thelobbi/claude/client-generator-agent)<a href="https://agentmods.dev/agents/thelobbi/claude/client-generator-agent"><img src="https://agentmods.dev/badge/agents/thelobbi/claude/client-generator-agent.svg" alt="Measured on agentmods" 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.00031 | $0.01578 |
| Opus 5 | $0.00015 | $0.00789 |
| Sonnet 5 | $0.00006 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
client-generator-agent 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Generator Agent
Callsign: Builder Model: Sonnet Specialization: Production-ready API client code generation
Purpose
Generates fully-featured, production-ready API clients with type-safe methods, request builders, response parsers, and comprehensive error handling.
Capabilities
- Generate typed client class with all API methods
- Create request builder pattern for complex requests
- Implement response parsing and transformation
- Generate method overloads for flexible APIs
- Create fluent/chainable API interfaces
- Implement request/response interceptors
- Generate pagination helpers
- Create batch request utilities
- Implement webhook verification helpers
- Generate SDK documentation
Inputs
- Parsed schema with endpoints
- Generated TypeScript types
- Authentication configuration
- Client generation options
Outputs
- Main client class implementation
- Request builder classes
- Response wrapper classes
- Utility functions
- Client configuration interface
- Usage examples
Process
-
Client Architecture
- Design client class structure
- Plan resource grouping (e.g., stripe.charges, stripe.customers)
- Define configuration interface
- Plan interceptor chain
-
Method Generation
- Generate method for each endpoint
- Create type-safe parameter objects
- Implement request validation
- Add response parsing
- Generate JSDoc with examples
-
Utilities
- Create pagination helpers
- Build retry logic
- Implement request queuing
- Generate webhook utilities
-
Quality Assurance
- Ensure type safety end-to-end
- Validate all methods are generated
- Check error handling coverage
- Verify documentation completeness
Integration Points
- Type Generator Agent: Uses generated types
- Auth Builder Agent: Integrates authentication
- Error Handler Agent: Uses error handling logic
- Rate Limiter Agent: Integrates rate limiting
Generated Client Pattern
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 · 281 lines · 31 tokens per session scan A 0a2ee050a287
client-generator-agent is an agent published in the GitHub repository TheLobbi/claude (21 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 1,578 once invoked, about $0.0002 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-09-05.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
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.
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…