Borrowing it
Nothing to install: this file belongs to krishnanpandya007/support-technician-setup. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/krishnanpandya007/support-technician-setup/master/.claude/skills/integrating-support-agent/SKILL.mdgit clone --depth 1 https://github.com/krishnanpandya007/support-technician-setupWrote 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/krishnanpandya007/support-technician-setup/integrating-support-agent)<a href="https://agentmods.dev/skills/krishnanpandya007/support-technician-setup/integrating-support-agent"><img src="https://agentmods.dev/badge/skills/krishnanpandya007/support-technician-setup/integrating-support-agent/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/krishnanpandya007/support-technician-setup/integrating-support-agent"><img src="https://agentmods.dev/badge/skills/krishnanpandya007/support-technician-setup/integrating-support-agent.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.00121 | $0.02586 |
| Opus 5 | $0.00060 | $0.01293 |
| Sonnet 5 | $0.00024 | $0.00517 |
| Haiku 4.5 | $0.00012 | $0.00259 |
Grade A, and why
integrating-support-agent 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 10d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrating the Support Agent
Overview
This is the last mile. The earlier stages produce a support kit; the operator then runs support-binder, applies the access migration, and fills .secrets — all locally, off-model. This skill takes that bound kit and the operator's end-user app and wires the two together, turning the kit's command-line runtime into a support endpoint real users reach from inside the app.
Core principle: follow the operator's practice; enforce the invariants regardless of it. Teams host things differently — a separate small service, a route inside the app, a serverless function, or an existing chat/helpdesk platform. This skill never prescribes a topology. It discovers the app's practice, confirms it, and generates the integration for that practice — while the five invariants below hold under every one of them. The repo-root INTEGRATION.md is the operator-facing companion: it explains the practices and their trade-offs in plain language; point the operator at it whenever a choice is theirs to make.
Prerequisites — stop and say so if missing: a complete support kit (harness/, tools/, runbooks/, persona.md, support.config.yaml); evidence the operator has done the local DB step (tools/ACCESS_SETUP.md and the *.local.* artifacts exist — you never read their contents beyond confirming presence); and the end-user app's source.
Universal vs practice-specific
Some artifacts are identical for every practice; generate them always. The rest exist only for the confirmed practice — never generate all variants speculatively.
| Always (universal) | Per-practice only |
|---|---|
| Chat endpoint contract (request/response + fail-closed rules) | Serving-layer code (service / route / function / platform adapter) |
| Session-bridge contract (verified session → user id → per-connection identity) | Session-bridge implementation (reuses the app's own verification) |
| Escalation wiring spec + fire-test script | End-user entry point (widget snippet / component edit / platform binding) |
SMOKE.md checklist + operator-run scripts |
Deployment glue (compose service / route registration / function config / platform setup) |
CHANGES.md review manifest |
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.
- 10d ago First seen · 111 lines · 0 tokens per session scan A a5bd316b54a7
integrating-support-agent is a skill published in the GitHub repository krishnanpandya007/support-technician-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 121 tokens to every session and 2,586 once invoked, about $0.0006 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-31.
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…