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 vincentkoc/dotskills --skill technical-integrationsgit clone --depth 1 https://github.com/vincentkoc/dotskillsWrote 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/vincentkoc/dotskills/technical-integrations)<a href="https://agentmods.dev/skills/vincentkoc/dotskills/technical-integrations"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/technical-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/vincentkoc/dotskills/technical-integrations"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/technical-integrations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00520 |
| Opus 5.5 | $0.00012 | $0.00208 |
| Sonnet 5.5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
technical-integrations 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Integrations
Purpose
Design and review external-vendor integrations using existing internal patterns, with vendor/framework-agnostic workflows for API, RFC, SDK, and rollout planning.
When to use
- Adding a new third-party/vendor integration.
- Evolving an existing integration surface without breaking compatibility.
- Writing or reviewing integration RFCs before implementation.
- Defining SDK/API integration points and delivery plans.
Workflow
- Classify mode:
discover,design,review, orimplementation-plan. - Run
references/hunt-and-inventory.mdto gather current integration evidence and patterns. - Use
references/principles.mdto enforce vendor/framework-agnostic constraints. - For architecture and proposal work, follow
references/design-and-rfc.md. - For execution sequencing, follow
references/implementation-plan.md. - For QA pass, apply
references/review-checklist.md. - Return deliverables with explicit decisions, tradeoffs, and open risks.
Flow
stateDiagram-v2
[*] --> ClassifyRequest
ClassifyRequest --> HuntAndInventory
HuntAndInventory --> ApplyPrinciples
ApplyPrinciples --> SelectWork
state SelectWork <<choice>>
SelectWork --> Deliverables: discovery only
SelectWork --> DesignAndRFC: architecture or proposal
SelectWork --> ImplementationPlan: execution sequencing
SelectWork --> ReviewChecklist: review
DesignAndRFC --> ReviewChecklist: QA pass in scope
DesignAndRFC --> Deliverables: proposal only
ImplementationPlan --> ReviewChecklist: QA pass in scope
ImplementationPlan --> Deliverables: plan only
ReviewChecklist --> Deliverables
Deliverables --> [*]
Inputs
- Integration objective and target vendor capability.
- Existing repo patterns (API, SDK, auth, observability, error model).
- Compatibility constraints (backward compatibility, versioning, rollout policy).
- Scope (discovery only, RFC draft, implementation plan, or full review).
What ships with it
7 files 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.
- 1mo ago Changed · +21 lines e5d12ccb2e56
- 1mo ago First seen · 45 lines · 31 tokens per session scan A 87e13c687fb9
technical-integrations is a skill published in the GitHub repository vincentkoc/dotskills (109 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 520 once invoked, about $0.0001 per session on Opus 5.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
webhook-subscriptions
Create and manage webhook subscriptions for event-driven agent activation. Use when the user wants external services (GitHub, GitLab, Stripe, Linear, PagerDuty, Sentry, or any generic source) to trigger agent runs by POSTing events to a URL.
service-app-creator
Create or update the Service component of a NextClaw Mini App, choosing between Portable Rust/WASI Components and native-process MCP services. Use after nextclaw-app-creator selects a Service-backed app, or when the user explicitly asks for Service Actions, portable components, local files, external APIs, commands…
add-api-endpoint
Guide for adding new API endpoints to the Platypus backend using Hono.js — routing, tenant scoping middleware, validation, and database access.
api-conventions
Response-body conventions for the Platypus backend API — the error key for failures, the message key for 2xx status messages, and when to throw a typed error instead of returning a response. Use when adding or changing a backend route or its tests.
go-context
Use when working with context.Context in Go — placement in signatures, propagating cancellation and deadlines, and storing values in context vs parameters. Also use when cancelling long-running operations, setting timeouts, or passing request-scoped data, even if they don't mention context.Context directly. Does not…
go-functional-options
Use when designing a Go constructor or factory function with optional configuration — especially with 3+ optional parameters or extensible APIs. Also use when building a New function that takes many settings, even if they don't mention "functional options" by name. Does not cover general function design (see…