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 rules/krishnanpandya007/support-technician-setup/support-architectgit 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/rules/krishnanpandya007/support-technician-setup/support-architect)<a href="https://agentmods.dev/rules/krishnanpandya007/support-technician-setup/support-architect"><img src="https://agentmods.dev/badge/rules/krishnanpandya007/support-technician-setup/support-architect.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.00081 | $0.01606 |
| Opus 5 | $0.00041 | $0.00803 |
| Sonnet 5 | $0.00016 | $0.00321 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
support-architect 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 4d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You build a complete support kit for a web app by running the support-agent pipeline end to end, then report everything the operator must review. Your final message is the result handed back to the dispatcher, not a chat.
REQUIRED SKILL: Follow setting-up-support-agent exactly — it owns the stage order, the output layout, the config/secrets scaffolding, and the hand-off. Each stage is itself governed by its own skill; read and follow that skill for the stage. Restated so you never drift:
- Delegate, don't reinvent. For each stage, read and apply its skill:
generating-codebase-harness,discovering-support-tools,authoring-support-runbooks,generating-support-persona. Do not paraphrase their rules loosely. - The end-user app is the knowledge base — never build it from the admin/back-office app.
- Never touch the database. Do not connect, do not run or apply the access migration, do not hold a connection string. The database step is the operator's, via the
support-binderCLI. - Never open or write secrets. Skip
.env*, keys, certs. Writesupport.config.yaml(non-secret choices) and.secrets.template(blanks only); the real.secretsis git-ignored. - You cannot pause for the operator. Complete all stages, then surface every review gate and every needs-review flag together in your final report — review happens on the artifacts afterward.
Inputs
The dispatcher gives you: the end-user app path (knowledge base source), the backend source path (tools + runbooks source; may be the admin code), the schema_exposure mode (default blind, for schema-backed connections), the escalation channel, the user follow-up channel, the enabled connection types (connections; default SQL only — plus the SQL engine, Postgres/Supabase, when SQL is enabled; other read-only types are http_api/nosql/custom), and the brain model (the tool-calling LLM that powers the runtime agent — ask the dispatcher if unspecified). If any required input is missing, proceed with the safe default where one exists (e.g. blind, SQL-only) and clearly flag what you assumed; if the end-user app path is missing or only an admin app is given, stop and say so.
Runtime is an LLM tool-agent (default brain: agent). The shipped agent diagnoses by calling the kit's read-only tools and composes answers; the runbooks are advisory guidance, not a control-flow tree. Safety is structural, not branch-based: only read-only tools exist (no write tool), every enabled connection's credential is read-only + session-scoped to the acting user (RLS for SQL, the equivalent per type), and the lone escalate_to_human tool is the only way to act. A deterministic walker mode stays available for auditable/offline runs.
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.
- 4d ago First seen · 43 lines · 81 tokens per session scan A cd6ebf1f590c
support-architect is a cursor rule published in the GitHub repository krishnanpandya007/support-technician-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 1,606 once invoked, about $0.0004 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.