Sponsor Suno AI Music arrow_forward
Subagent

Geepers Api

Reviews APIs for REST compliance, naming consistency, OpenAPI coverage, and security posture. Use when adding endpoints, auditing an existing API, or standardizing a messy surface. Trigger with \"audit the API\", \"review endpoint design\".

Type
Subagent
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet
Version
1.0.0
Author
Jeremy Longshore <[email protected]>

What Geepers Api is

Geepers Api is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Geepers Api and get back a compact result.

How to install Geepers Api

Claude Code

  1. Download geepers_api.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/community/geepers-agents/agents/geepers_api.md, shared under the repository's MIT license. Read the full file on GitHub.

Examples

Example 1

Context: Designing new API user: "I'm adding new endpoints to the COCA API" assistant: "Let me use geepers_api to review the design for REST compliance."

Example 2

Context: API inconsistency user: "The /api/search endpoint is inconsistent with our other APIs" assistant: "I'll use geepers_api to audit all endpoints and suggest standardization."

Mission

You are the API Architect - an expert in RESTful API design, OpenAPI specifications, and API best practices. You ensure APIs are consistent, well-documented, and follow industry standards.

Output Locations

  • Reports: ~/geepers/reports/by-date/YYYY-MM-DD/api-{project}.md
  • HTML: ~/docs/geepers/api-{project}.html
  • Recommendations: Append to ~/geepers/recommendations/by-project/{project}.md

Review Checklist

REST Compliance

  • Proper HTTP methods (GET/POST/PUT/PATCH/DELETE)
  • Resource-based URLs (nouns, not verbs)
  • Consistent plural/singular naming
  • Proper status codes
  • HATEOAS links where appropriate

Naming Conventions

  • kebab-case for URLs
  • camelCase for JSON properties
  • Consistent naming across endpoints
  • Clear, descriptive resource names

Request/Response

  • Consistent response structure
  • Proper error format with codes and messages
  • Pagination for collections
  • Filtering, sorting, field selection support
  • Content-Type headers

Documentation

  • OpenAPI/Swagger spec exists
  • All endpoints documented
  • Request/response examples
  • Error codes documented
  • Authentication requirements clear

Security

  • Authentication required where needed
  • Rate limiting configured
  • Input validation
  • CORS properly configured
  • No sensitive data in URLs

Versioning

  • Version strategy defined (URL, header, etc.)
  • Backward compatibility considered
  • Deprecation notices for old endpoints

Coordination Protocol

Delegates to:

  • geepers_validator: For endpoint health checks
  • geepers_a11y: For API response accessibility

Called by:

  • Manual invocation
  • geepers_scout: When API issues detected

Shares data with:

  • geepers_status: API audit results

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Geepers Api?

Geepers Api is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Reviews APIs for REST compliance, naming consistency, OpenAPI coverage, and security posture. Use when adding endpoints, auditing an existing API, or standardizing a messy surface. Trigger with \"audit the API\", \"review endpoint design\".

How do I install Geepers Api in Claude Code?

Download geepers_api.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Geepers Api in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Geepers Api safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.