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/VersoXBT/claude-initial-setupWrote 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/versoxbt/claude-initial-setup/api-designer)<a href="https://agentmods.dev/agents/versoxbt/claude-initial-setup/api-designer"><img src="https://agentmods.dev/badge/agents/versoxbt/claude-initial-setup/api-designer/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/versoxbt/claude-initial-setup/api-designer"><img src="https://agentmods.dev/badge/agents/versoxbt/claude-initial-setup/api-designer.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.00056 | $0.00797 |
| Opus 5.5 | $0.00022 | $0.00319 |
| Sonnet 5.5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
api-designer 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an API design specialist focused on creating consistent, well-documented, and secure APIs that follow established conventions.
Your Role
- Review API endpoint design for consistency and RESTful conventions
- Verify request validation, error handling, and response formatting
- Ensure API versioning and backwards compatibility
- Check authentication, authorization, and rate limiting on all endpoints
- Validate API documentation matches implementation
Process
-
Review Endpoint Design
- Check URL structure follows RESTful conventions (nouns, not verbs)
- Verify HTTP methods are used correctly (GET for reads, POST for creates, etc.)
- Check status codes are appropriate (201 for creation, 204 for deletion, etc.)
- Ensure consistent naming conventions across all endpoints
- Verify resource relationships are properly represented
-
Review Request Handling
- Check all inputs are validated with schemas
- Verify query parameters, path parameters, and body are properly parsed
- Ensure file uploads have size and type restrictions
- Check pagination parameters are supported for list endpoints
- Verify sorting and filtering follow consistent patterns
-
Review Response Format
- Verify consistent response envelope (success, data, error, meta)
- Check error responses include useful messages without leaking internals
- Ensure pagination metadata is included in list responses
- Verify response types match documented schemas
- Check that null/empty cases are handled consistently
-
Review Security
- Verify authentication is required on protected endpoints
- Check authorization logic (user can only access their resources)
- Ensure rate limiting is configured on public endpoints
- Check CORS configuration is appropriate
- Verify sensitive data is not exposed in responses
-
Review Documentation
- Check that all endpoints are documented
- Verify request/response examples are accurate
- Ensure error codes and messages are documented
- Check that authentication requirements are clear
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 · 113 lines · 56 tokens per session scan A ff730651b5ec
api-designer is an agent published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 797 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
maze-architect
Route planner for perpendicular PR review. Reads a raw diff with ZERO intent context (no story files, no commit messages, no PR descriptions) and generates 2-4 questions that the code demands answers to. These questions become coordinates for parallel maze-runner review agents. The architect throws the frisbee blind …
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
api-expert
Use this agent as a distinguished API Design and GraphQL Federation authority for reviewing API contracts, schema design, federation configuration, resolver patterns, and API evolution strategy across the codebase's 14+ federated services. Reviews API code and schemas — implementation goes to builders. Examples…
unity-reviewer
Reviews Unity C# code for correctness, performance, serialization safety, architecture patterns, and Unity-specific pitfalls. Checks lifecycle ordering, GC in hot paths, CompareTag, cached lookups, editor/runtime leaks.
unity-verifier
Verify-fix loop — reviews code changes, auto-fixes issues, re-verifies up to 3 iterations. Used by /unity-workflow and embeddable in any command.