api-integration-specialist

An agent for designing and implementing APIs, which are defined ways for software systems to communicate. It covers internal B2B applications, where one business provides software to another.

In plain words
What is it for?
Use it for REST or GraphQL APIs, API documentation, software development kits, developer portals, performance improvements, versioning, and communication between internal services.
Why use it?
It helps organize API architecture and developer-facing materials, reducing problems with unclear interfaces, missing documentation, version changes, or difficult integrations.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add lifangda/claude-plugins
agentmods
npx agentmods add plugins/lifangda/claude-plugins/api-integration-specialist
Clone the repo
git clone --depth 1 https://github.com/lifangda/claude-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

api-integration-specialist 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.

backups/legacy_backup_20251015/claude-code-marketplace-main/plugins/api-integration-specialist/.claude-plugin/plugin.json · 14 lines

What it actually says

{
  "name": "api-integration-specialist",
  "description": "Use this agent when you need to design and implement internal API architecture, developer experience, and API infrastructure for B2B applications. This agent specializes in REST API design, GraphQL implementation, API documentation, SDK development, and developer portal creation. Handles API performance optimization, versioning strategies, and internal service communication. Examples:",
  "version": "1.0.0",
  "author": {
    "name": "Alysson Franklin"
  },
  "category": "agents",
  "homepage": "https://claudecodecommands.directory/agents/api-integration-specialist",
  "keywords": [
    "subagent"
  ],
  "agents": "./agents/"
}
Changes

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.

  1. 2d ago First seen · 14 lines scan A d5cd4dedb9c5

Subscribe to this mod's changes

api-integration-specialist is a plugin published in the GitHub repository lifangda/claude-plugins (43 stars, last pushed 10mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.