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 Omar-Obando/qwen-orchestrator --skill third-party-integrationsgit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/third-party-integrations)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/third-party-integrations"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/third-party-integrations/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/skills/omar-obando/qwen-orchestrator/third-party-integrations"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/third-party-integrations.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.00032 | $0.04300 |
| Opus 5 | $0.00016 | $0.02150 |
| Sonnet 5 | $0.00006 | $0.00860 |
| Haiku 4.5 | $0.00003 | $0.00430 |
Grade B, and why
third-party-integrations scanned grade B with 1 finding 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 9d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const response = await fetch('https://provider.com/oauth/token', { method: 'POST', How it starts
The opening of the file, as written. The whole thing — 758 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Third-Party Integration Strategy
When integrating with third-party services (webhooks, REST APIs, SOAP, OAuth, payment gateways, email services), follow this systematic approach to avoid common pitfalls and ensure maintainability.
Integration Types Overview
| Type | Use Case | Complexity | Maintenance | Example Services |
|---|---|---|---|---|
| Webhooks | Receive real-time notifications | Medium | Low | Stripe, GitHub, Slack |
| REST API | CRUD operations | Low-Medium | Medium | Stripe, PayPal, SendGrid |
| SOAP | Legacy systems, enterprise | High | High | Banking systems, legacy ERP |
| OAuth | User authorization | Medium | Medium | Google, Facebook, GitHub |
| Email APIs | Send/receive emails | Low | Medium | SendGrid, Mailgun, SES |
Integration Decision Tree
What do you need to integrate?
├─ Real-time notifications?
│ ├─ Yes → Webhooks
│ │ ├─ Need to verify signatures? → Yes → Implement signature verification
│ │ └─ Need to handle retries? → Yes → Implement retry queue
│ └─ No → Continue
├─ CRUD operations?
│ ├─ Yes → REST API
│ │ ├─ Simple CRUD? → Yes → Direct client
│ │ └─ Complex operations? → No → Service layer pattern
│ └─ No → Continue
├─ Legacy enterprise system?
│ ├─ Yes → SOAP
│ │ ├─ WSDL available? → Yes → Generate client from WSDL
│ │ └─ No WSDL? → No → Document-first design
│ └─ No → Continue
└─ User authentication?
├─ Yes → OAuth 2.0
│ ├─ Google/Facebook/GitHub? → Yes → Use official SDK
│ └─ Custom auth server? → No → Implement OAuth flow
└─ No → Continue
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 758 lines · 32 tokens per session scan B 3f710c1c87b8
third-party-integrations is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 4,300 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
afm
Maintain and extend AFM (maclocal-api), a Swift OpenAI-compatible local LLM server and CLI for Apple Foundation Models, MLX models, API gateway proxying, and Vision OCR. Use when working on AFM CLI commands (afm, afm mlx, afm vision), OpenAI /v1/chat/completions and /v1/models behavior, streaming SSE, tool-calling…
hue
Read and control Philips Hue Bridge lighting installations through local CLIP v2 or the Hue Remote API with SecretRef-backed credentials and guarded lighting changes.
google-ads
Manage Google Ads accounts with safe GAQL reporting, campaign planning, guarded mutations, and gateway-proxied REST API calls.
lexware-office
Work with Lexware Office contacts, products, invoices, quotations, bookkeeping vouchers, receipts, payment status, and guarded invoice, quotation, or expense writes through the Public API.
miro
Discover Miro boards, read board items for planning and summaries, prepare guarded board writes, and run Enterprise board export workflows through SecretRef-backed API requests.
fronius
Read Fronius photovoltaic inverter data through the local Fronius Solar API V1 or Solar.web Query API cloud, without exposing access-key material.