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 agentmods add skills/vincentkoc/dotskills/technical-integrationsnpx 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.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 | $0.00031 | $0.00363 |
| Opus 5 | $0.00015 | $0.00181 |
| Sonnet 5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
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 3d 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.
What it actually says
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.
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).
Outputs
- Integration inventory and pattern baseline.
- RFC-quality proposal with options and decision rationale.
- API and SDK integration design plan.
- Validation and rollout checklist with unresolved risks.
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.
- 3d ago First seen · 45 lines · 31 tokens per session scan A 87e13c687fb9
technical-integrations is a skill published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed 12d ago), licensed MIT. It adds 31 tokens to every session and 363 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-30.
Other skills, from other repositories
panel-app-creator
Create or update the Panel App UI part of a NextClaw lightweight app. Use after nextclaw-app-creator selects Panel-only or Panel + Service, or when the user explicitly asks for a right-side Panel App UI, folder-based static panel, Service Actions UI, Agent-powered Panel App, React/Vite/Tailwind Panel App, or asks what…
service-app-creator
Create or update the Service App backend action part of a NextClaw lightweight app. Use after nextclaw-app-creator selects Service-only or Panel + Service, or when the user explicitly asks for workspace service-apps, MCP-compatible backend helpers, file access, external API calls, local commands, or privileged actions.
nextclaw-dead-code-governance
当用户要求扫描、识别、清理、常态化治理 NextClaw 仓库里的死代码、无用代码、unused files、unused exports、unused dependencies，尤其是核心包越来越臃肿、想删旧实现或做定期减债时使用。.
nextclaw-http-agent-runtime-integration
Use when integrating or debugging a Hermes-style external HTTP agent runtime in NextClaw, including runtime config, session selection, readiness, streaming, and adapter behavior.
nextclaw-product-visual-assets
当 NextClaw 产品更新后需要生成、替换、挑毛病或检查官网、GitHub README、用户文档或社交传播中的真实截图、AI 宣传视觉、整页 HTML 宣传预览、社区二维码等对外视觉资产时使用；也用于“更新截图”“重新截一批图”“做宣传页”“生成 campaign 页面”“视觉审稿”“五星挑刺法”或发布前检查视觉资产。普通站点布局开发或只写文章不触发。.
agent-browser
Use Agent Browser for real browser navigation, dynamic pages, and web interaction; also use it as a distinct browser-based path when websearch is unavailable or fails.