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 DorianSchlede/nexus-template --skill add-integrationgit clone --depth 1 https://github.com/DorianSchlede/nexus-templateWrote 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/dorianschlede/nexus-template/add-integration)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/add-integration"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/add-integration/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/dorianschlede/nexus-template/add-integration"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/add-integration.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.00018 | $0.03653 |
| Opus 5 | $0.00009 | $0.01826 |
| Sonnet 5 | $0.00004 | $0.00731 |
| Haiku 4.5 | $0.00002 | $0.00365 |
Grade A, and why
add-integration 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 8d 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 — 619 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Awareness (CHECK BEFORE STARTING)
Before building an integration, AI MUST check stats.pending_onboarding for learn_integrations:
Pre-Flight Check (RECOMMENDED)
Check if learn_integrations is in stats.pending_onboarding. If present:
💡 Before building your first integration, would you like a quick 10-minute
tutorial on how Nexus integrations work? It covers:
- What MCP (Model Context Protocol) is
- Available integration patterns
- When to use integrations vs other approaches
Say 'learn integrations' to start the tutorial, or 'skip' to build directly.
If user says 'skip': Proceed with integration building but add this note at the end:
💡 Tip: Run 'learn integrations' later to understand the integration ecosystem.
If learn_integrations NOT in pending_onboarding: Proceed normally without suggestion.
Context Awareness
If user mentions connecting to external tools but learn_integrations is pending:
- Gently suggest learning first if they seem unfamiliar with MCP concepts
- Skip suggestion if they clearly know what they're doing (e.g., mention specific API endpoints)
Add Integration
Build complete API integrations following the master/connect/specialized pattern.
[!] CRITICAL: MUST LOAD plan-build SKILL [!]
MANDATORY: In Step 4, load the plan-build skill:
nexus-load --skill plan-build
Then follow its workflow to create the integration build.
Purpose
The add-integration skill transforms API documentation into a complete, production-ready integration. It:
- Discovers available API endpoints via web search
- Presents endpoints for user selection
- Plans the integration architecture
- Creates a build for implementation (via plan-build skill)
Architecture Pattern: See references/integration-architecture.md
What ships with it
18 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.
- references/integration-architecture.md 5.8 KB
- references/integration-ideas.md 13 KB
- references/mcp-guide.md 11 KB
- references/mcp-introduction.md 7.6 KB
- references/mcp-setup-guide.md 13 KB
- references/troubleshooting-guide.md 15 KB
- scripts/scaffold_integration.py 30 KB runs code
- templates/api-client.py.template 3.5 KB
- templates/config-check.py.template 4.9 KB
- templates/connect-skill.md.template 2.6 KB
- templates/master-skill.md.template 3.9 KB
- templates/operation-script.py.template 1.8 KB
- templates/operation-skill.md.template 1.3 KB
- templates/references/api-reference.md.template 982 B
- templates/references/authentication.md.template 1.3 KB
- templates/references/error-handling.md.template 2.3 KB
- templates/references/setup-guide.md.template 1.7 KB
- templates/setup-wizard.py.template 4.1 KB
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.
- 8d ago First seen · 619 lines · 18 tokens per session scan A 970ad0c21c18
add-integration is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 3,653 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…