Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add satriotsubasa/PowerPlatform-Core/plugin install powerplatform-coreWrote 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/satriotsubasa/powerplatform-core/custom-connectors)<a href="https://agentmods.dev/skills/satriotsubasa/powerplatform-core/custom-connectors"><img src="https://agentmods.dev/badge/skills/satriotsubasa/powerplatform-core/custom-connectors/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/satriotsubasa/powerplatform-core/custom-connectors"><img src="https://agentmods.dev/badge/skills/satriotsubasa/powerplatform-core/custom-connectors.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.00182 | $0.00998 |
| Opus 5 | $0.00091 | $0.00499 |
| Sonnet 5 | $0.00036 | $0.00200 |
| Haiku 4.5 | $0.00018 | $0.00100 |
Grade A, and why
custom-connectors 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 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.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Connectors and Integration Wrappers
This skill helps design how Power Platform talks to an external API: reviewing the API description, settling the authentication shape, inventorying operations, and — critically — recommending whether the integration should be a direct custom connector or sit behind an Azure Function / API facade. It is design-first. It produces a reviewed structure and recommendation; the actual connector publish or Azure delivery still needs its own implementation path. Keep the result solution-aware with explicit connection references and environment variables so it promotes cleanly across environments.
When to use this
- Review an OpenAPI/Swagger document or a structured integration requirement for connector suitability.
- Recommend an auth approach and inventory the operations to expose.
- Decide direct custom connector vs Azure Function / API facade.
- Plan the environment variables and connection references the integration needs for ALM.
For the flow that will call the connector, use power-automate-flows. For server-side logic inside Dataverse, use plugins-server-extensions.
Helpers
Helpers live in the plugin's scripts/ directory at the plugin root, not inside this skill folder. Resolve the plugin root and invoke them:
- Claude Code:
python "$CLAUDE_PLUGIN_ROOT/scripts/design_custom_connector.py" --help - Codex:
python "$CODEX_PLUGIN_ROOT/scripts/design_custom_connector.py" --help(also exposed as$PLUGIN_ROOT) - Standalone / unsure: the
scripts/folder sits beside this skill bundle; invoke by its path within the install.
| Helper | Use it to |
|---|---|
design_custom_connector.py |
Review an OpenAPI description or structured requirement and emit a connector name, auth approach, operation summaries, a recommended pattern (direct connector vs facade), suggested environment variables, and connection-reference guidance. |
Workflow
- Inspect the source. Read the OpenAPI/Swagger description or the structured integration requirement before deciding anything.
- Judge direct-connector fit. A clean, REST-shaped, JSON API with standard auth is a good direct custom-connector candidate.
- Prefer a facade when the shape is hard. If the integration involves binary payloads, heavy transformation, fan-out/orchestration, or non-REST behavior, recommend an Azure Function (or similar) facade first and expose that as the connector.
- Settle auth. Recommend the auth approach (API key, OAuth2, basic, none) that matches the API and the platform's supported connector auth types.
- Keep it solution-aware. Plan explicit connection references and environment variables so credentials are not hardcoded and the connector promotes across Dev → Test → Prod.
- Hand off delivery. State clearly what still needs a separate implementation path: publishing the connector, or building and deploying the Azure facade.
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 · 61 lines · 182 tokens per session scan A 8dd18deffa59
custom-connectors is a skill published in the GitHub repository satriotsubasa/PowerPlatform-Core (17 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 182 tokens to every session and 998 once invoked, about $0.0009 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-30.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.