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/.github/copilot-instructions.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/instructions/krishnanpandya007/support-technician-setup/copilot-instructions)<a href="https://agentmods.dev/instructions/krishnanpandya007/support-technician-setup/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/krishnanpandya007/support-technician-setup/copilot-instructions.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.1 | $0.00674 | $0.00674 |
| Opus 5 | $0.00337 | $0.00337 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
support-technician-setup copilot-instructions.md 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 6d 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
Support Technician — Copilot instructions
This repository is a methodology bundle for building a read-only customer-support
agent from a codebase. When asked to build or set up a support agent, follow the
prompt files in .github/prompts/ (invoke with /) — for a full build, in this order:
/authoring-support-runbooks— Use when authoring the diagnostic runbooks a customer-support agent follows at runtime — turning a product's failure surface, its harness, and its read-only tool catalog into symptom-to-resolution decision trees plus synthetic evaluation tickets, for mandatory human review. Triggers: "author the support runbooks", "build the diagnostic decision trees", part of setting up a support agent./discovering-support-tools— Use when generating the read-only data-access tools a customer-support agent uses to diagnose an end user's live state — reading a project's backend to propose a tool catalog plus the database access SQL (restricted read-only role, column grants, row-level security), for mandatory human review. Triggers: "discover support tools", "generate the read-only tools / DB access for the support agent", part of setting up a support agent./generating-codebase-harness— Use when turning a codebase into a sanitized plain-language help-center knowledge base ("harness") for an AI support assistant — reading one or more project roots and producing navigable Markdown that describes user-facing behavior with no technical detail and no security mechanisms or secrets. Triggers: "build a harness", "help-center knowledge base from code", "sanitized docs for a support bot"./generating-support-persona— Use when generating a project-specific customer-support assistant persona from the reference template — turning a harnessed product's knowledge base and tool catalog into a finished persona.md for the runtime support agent. Triggers: "generate the support persona", "make the assistant persona for ", part of setting up a support agent./integrating-support-agent— Use to integrate a built support kit into the operator's real end-user app — discovers the app's own serving, session, frontend, and deployment practice and generates, for that practice, the session bridge (verified user id → per-connection identity), the chat serving layer, the end-user entry point, real escalation wiring, deployment glue, and an operator-run smoke-test checklist, all for mandatory human review. Triggers: "integrate the support agent", "wire the support kit into my app", "add the support chat to ", "deploy the support agent"./setting-up-support-agent— Use to set up a full customer-support agent for a web app — orchestrates the whole build pipeline (knowledge base, read-only tools + access SQL, diagnostic runbooks, persona, config/secrets scaffolding) by running the four stage skills in order, with a human-review gate after each, and hands off the local database step to the support-binder CLI. Triggers: "set up a support agent for ", "stand up the support kit", "build the full support pipeline".
Specialized agents live in .github/agents/. The safety contract is non-negotiable: the generated support agent is read-only, never writes data, and escalates changes to a human.
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.
- 6d ago First seen · 15 lines · 674 tokens per session scan A 7649c196545e
support-technician-setup copilot-instructions.md is an instructions file published in the GitHub repository krishnanpandya007/support-technician-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 674 tokens to every session, about $0.0034 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.