support-operations

support-operations is a skill for Claude Code, Codex from ncklrs/startup-os-skills. It costs 92 tokens per session (1,706 once invoked), scanned A, original, no licence file.

Customer support operations guidance for organizing service teams and their work. It covers ticket handling, service targets, support levels, escalations, knowledge bases, and support measurements.

In plain words
What is it for?
Use it to design ticket systems, service-level agreements, L1/L2/L3 support tiers, severity rules, escalation paths, knowledge bases, and metrics such as customer satisfaction and response time.
Why use it?
It helps remove guesswork from deciding how customer requests are prioritized, assigned, escalated, and measured.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to design ticket systems, service-level agreements, L1/L2/L3 support tiers, severity rules, escalation paths, knowledge bases, and metrics such as customer satisfaction and response time.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ncklrs/startup-os-skills/support-operations
Install

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.

Any agent
npx skills add ncklrs/startup-os-skills --skill support-operations
Clone the repo
git clone --depth 1 https://github.com/ncklrs/startup-os-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for support-operations

README.md
[![agentmods](https://agentmods.dev/badge/skills/ncklrs/startup-os-skills/support-operations/github.svg)](https://agentmods.dev/skills/ncklrs/startup-os-skills/support-operations)
Your own site
<a href="https://agentmods.dev/skills/ncklrs/startup-os-skills/support-operations"><img src="https://agentmods.dev/badge/skills/ncklrs/startup-os-skills/support-operations/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.

agentmods 80×15 button for support-operations

Your own site · 80×15
<a href="https://agentmods.dev/skills/ncklrs/startup-os-skills/support-operations"><img src="https://agentmods.dev/badge/skills/ncklrs/startup-os-skills/support-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,706 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.01706
Opus 5 $0.00046 $0.00853
Sonnet 5 $0.00018 $0.00341
Haiku 4.5 $0.00009 $0.00171

Measured 13d ago against content hash 049623b9efa3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

support-operations 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 13d 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.

skills/support-operations/SKILL.md · 161 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 13d ago First seen · 161 lines · 92 tokens per session scan A 049623b9efa3

Subscribe to this mod's changes

support-operations is a skill published in the GitHub repository ncklrs/startup-os-skills (50 stars, last pushed 6mo ago), with no licence file. It adds 92 tokens to every session and 1,706 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

tracking-todos

Maintain a structured task list for the current session. Use proactively when a request requires 3+ distinct steps, the user provides multiple items, or complex work benefits from explicit progress tracking. Storage persists via Muninn config across container death. Adapted from Claude Code's TodoWrite tool.

oaustegard/claude-skills · 61 tokens

closing-issues

Close a GitHub issue with a synthesis comment as a flowing graph — validate the synthesis, post the closing comment, close, then run a pluggable callback (e.g. memory store) detached. Use when closing an issue should also capture the LEARNING (not just the diff log) and when the post-close work shouldn't block the…

oaustegard/claude-skills · 75 tokens

Linear

Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.

wrsmith108/linear-claude-skill · 32 tokens

notion-spec-to-implementation

Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.

Prat011/awesome-llm-skills · 50 tokens

scrum-master-agent

Comprehensive Scrum Master assistant for sprint planning, backlog grooming, retrospectives, capacity planning, and daily standups with intelligent context-aware reporting.

alirezarezvani/claude-code-skill-factory · 32 tokens

Yandex Tracker

Manage Yandex Tracker spaces through the REST API. Use when Codex needs to work with any documented Tracker API function: issues, issue filters, checklists, comments, attachments, bulk operations, fields, projects, portfolios, goals, queues, automation, boards, dashboards, components, issue types, statuses…

18studio/yandex-tracker-skill · 89 tokens