A frontend integration command that connects an existing application to an API described in a specification or endpoint document.

Use it to map HTTP calls and placeholders, clarify authentication and response formats, build an organized API layer, and test the integration.

It prevents partial integrations, inconsistent API code, broken screens, and continued use of mock data.

integrate — Command for Claude Code by boparaiamrit/skills-by-amrit

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.

Clone the repo

git clone --depth 1 https://github.com/boparaiamrit/skills-by-amrit

Made for: Claude Code.

Or install skills-by-amrit, the plugin that ships this one along with the rest of its 33 skills, 34 commands, 9 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/integrate/github.svg)](https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/integrate)

Your own site

<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/integrate"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/integrate/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/integrate"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/integrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 743 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00033	$0.00743
Opus 5.5	$0.00013	$0.00297
Sonnet 5.5	$0.00007	$0.00149
Haiku 4.5	$0.00003	$0.00074

Measured 1mo ago against content hash eafa2877efa5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

integrate 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.

commands/integrate.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/integrate — Full-Stack API Integration

Integrate an API from a product manager's spec/doc into the existing frontend. Prevents partial integration, broken pages, and placeholder-driven development.

Prerequisites

API spec, documentation, Postman collection, or endpoint description
Existing frontend codebase to integrate into

Instructions

Step 1: Understand the API Spec

From $ARGUMENTS:

If a URL: Fetch and parse the API documentation
If "from clipboard": Ask the user to paste the spec
If a description: Parse the endpoint details

ASK the Iron Questions (BLOCKING if unanswered):

Base URL?
Auth method? (JWT, API key, session)
Response envelope format?
All endpoints with request/response shapes?
Error codes and their meanings?
Rate limits?
Pagination style?

Step 2: Map the Integration Surface

Search the ENTIRE codebase for every file that:

Makes HTTP calls
Uses mock/placeholder data
Has TODO/FIXME about API integration
Imports mock data files

grep -rn "fetch\|axios\|useSWR\|useQuery\|mock\|placeholder\|lorem\|fake\|dummy\|TODO.*api" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" . | grep -vi "node_modules\|.git\|dist\|.next\|test\|spec" | head -50

Step 3: Design the API Layer (SOLID)

Design and present to the user:

API client module (auth, errors, retry)
Service modules per domain entity
Type definitions for all shapes
Hook/composable layer

Step 4: Implement Endpoint by Endpoint

For EACH endpoint:

Types → API client → Service → Hook → Component updates → Integration test
Update EVERY file in the surface map for this endpoint
Verify build passes after each endpoint

Step 5: Verify No Mock Data Remains

grep -rn "mock\|placeholder\|lorem\|fake\|dummy\|hardcoded" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" . | grep -vi "node_modules\|.git\|dist\|.next\|test\|spec\|__mock"

Read the full file on GitHub · 93 lines

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.

1mo ago First seen · 93 lines · 33 tokens per session scan A eafa2877efa5

Subscribe to this mod's changes

integrate is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 743 once invoked, about $0.0001 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.

Backend and APIs Frontend

init

Initialize configurations for Supabase local development.

fcakyon/claude-codex-settings · 0 tokens

http-service

Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.

MadAppGang/magus · 27 tokens

build

Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.

Azure/ai-gateway · 0 tokens

api-contract-review

Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).

Mozurok/fhorja.dev · 64 tokens

start-10-1

A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.

minicoohei/ai-agent-camp · 2 tokens

fastapi

FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…

mfmezger/ai_agent_dotfiles · 84 tokens