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/boparaiamrit/skills-by-amritWrote 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/commands/boparaiamrit/skills-by-amrit/integrate)<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.
<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>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 | $0.00016 | $0.00371 |
| Sonnet 5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00074 |
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.
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
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:
- 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"
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.
- 10d ago First seen · 93 lines · 33 tokens per session scan A eafa2877efa5
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.
Other commands, from other repositories
rpc-client
Generate type-safe RPC client from Hono server routes.
azure-dotnet-webapp:webapp-setup
Interactive setup wizard for ASP.NET Core Web API or Blazor projects on Azure — selects project type, auth, database, and Graph integration; scaffolds the full project structure with compilable stubs; and verifies the build.
frappe-fullstack
Invoke multiple Frappe agents in parallel for full-stack development - coordinates backend, frontend, and architecture agents for complete feature implementation.
add-seo
Add comprehensive SEO to a page using Next.js 15 Metadata API.
add-table
Create advanced data table component with rich features. Implement column sorting (ascending/descending) with multi-column support. Add pagination with page size selector and jump to page. Implement client-side and server-side filtering. Add column visibility toggle with saved preferences. Implement row selection with…
add-seo
Add comprehensive SEO to a page using Next.js 15 Metadata API.