integrate

integrate is a command for Claude Code from boparaiamrit/skills-by-amrit. It costs 33 tokens per session (743 once invoked), scanned A, original, MIT.

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

In plain words
What is it for?
Use it to map HTTP calls and placeholders, clarify authentication and response formats, build an organized API layer, and test the integration.
Why use it?
It prevents partial integrations, inconsistent API code, broken screens, and continued use of mock data.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the skills-by-amrit plugin — 33 skills, 34 commands, 9 agents shipped together

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

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/boparaiamrit/skills-by-amrit/integrate
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.

agentmods badge for integrate

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.

agentmods 80×15 button for integrate

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00743
Opus 5 $0.00016 $0.00371
Sonnet 5 $0.00007 $0.00149
Haiku 4.5 $0.00003 $0.00074

Measured 10d ago against content hash eafa2877efa5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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):

  1. Base URL?
  2. Auth method? (JWT, API key, session)
  3. Response envelope format?
  4. All endpoints with request/response shapes?
  5. Error codes and their meanings?
  6. Rate limits?
  7. 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

Create a Surface Map table: | File | Current State | API Endpoint(s) | What Needs to Change |

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:

  1. Types → API client → Service → Hook → Component updates → Integration test
  2. Update EVERY file in the surface map for this endpoint
  3. 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.

  1. 10d 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 5mo ago), licensed MIT. It adds 33 tokens to every session and 743 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-08-31.