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.
npx skills add rpraharaj/forward-deployed-engineer --skill integration-adaptergit clone --depth 1 https://github.com/rpraharaj/forward-deployed-engineerWrote 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/skills/rpraharaj/forward-deployed-engineer/integration-adapter)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/integration-adapter"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/integration-adapter.svg" alt="Measured on agentmods" 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.00101 | $0.02255 |
| Opus 5 | $0.00051 | $0.01128 |
| Sonnet 5 | $0.00020 | $0.00451 |
| Haiku 4.5 | $0.00010 | $0.00226 |
Grade A, and why
integration-adapter 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 7d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration adapter
Talking to something you can't change.
Why this exists
Enterprise integration is mostly against systems that are undocumented, documented incorrectly, owned by someone else, or all three. A mainframe interface described by a Word document from 2014. A partner SOAP endpoint whose WSDL doesn't match what it returns. A flat file whose format is defined by the code that writes it.
Two assumptions make this work, and both feel pessimistic until you've been burned:
The documentation is wrong. Not maliciously — it described the system accurately once. Observed behavior beats documentation every time, and where they disagree, the documentation is the thing that's out of date.
The interface will misbehave. It will time out, return malformed responses, return HTTP 200 with an error in the body, be down for maintenance without notice, and change without telling you. An adapter that assumes good behavior fails in production in ways that are hard to diagnose because the failure is somewhere you can't see.
When this applies
- Consuming a legacy, mainframe, SOAP, flat-file, or externally-owned interface
- Documentation disagrees with reality
- Partner or vendor system integration
- The system on the other side can't be changed
When it doesn't
- Both sides are yours and changeable — design the contract properly with
contract-design - A well-maintained internal API with an accurate spec
- You need to understand an existing integration rather than build one — that's
trace-the-flow
Prerequisites
- Locate the workspace:
FDE_WORKSPACE, else the charter Location, else.fde/, else../<repo>-fde/ .fde/02-system-map.md— where this integration sits.fde/03b-nfrs.md— what data may cross the boundary- Any existing callers of the same system, which are your best documentation
Procedure
1. Find the existing callers first
Before reading any specification, find code in the organization that already talks to this system. It encodes years of accumulated knowledge about the interface's actual behavior — every workaround in it is a bug someone hit.
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.
- 7d ago First seen · 188 lines · 101 tokens per session scan A c55c51819588
integration-adapter is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 20d ago), licensed MIT. It adds 101 tokens to every session and 2,255 once invoked, about $0.0005 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 skills, from other repositories
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
memstack-automation-webhook-designer
Use this skill when the user says 'webhook', 'webhook handler', 'webhook endpoint', 'receive events', 'HMAC verification', 'idempotency', or needs secure webhook handlers with signature verification, retry handling, and dead letter queues. Do NOT use for full n8n workflows or scheduled tasks.
telegram
Owner-only Telegram text bridge and Mini App gateway for the existing Ouroboros interface.
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
agentsecrets
Zero-knowledge secrets infrastructure — AI agents manage the complete credential lifecycle without ever seeing values.