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 shanananana/deepticket --skill config-querygit clone --depth 1 https://github.com/shanananana/deepticketWrote 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/shanananana/deepticket/config-query)<a href="https://agentmods.dev/skills/shanananana/deepticket/config-query"><img src="https://agentmods.dev/badge/skills/shanananana/deepticket/config-query.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00300 |
| Opus 5 | $0.00016 | $0.00150 |
| Sonnet 5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
config-query 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.
What it actually says
配置查询 Skill
这是 DeepTicket 内置的 Skill 模板。请替换为你们公司真实的配置查询逻辑。
适用场景
- 排查「配置不一致」「开关未打开」「环境配错」类工单
- 需要对比 test / staging / prod 配置差异
- 需要查询某个服务的关键配置项
实现指引（由用户团队自行替换）
- 在
skills/config-query/scripts/添加配置查询脚本 - 填写配置中心地址、命名空间、应用名规则
- 输出时 脱敏 API Key、密码等字段
示例流程
- 从工单识别服务名、环境、配置 key
- 调用内部配置 API（占位）
- 返回当前值 + 最近变更记录（如有）
- 判断是否与代码/文档预期一致
占位 API（请替换）
- 配置中心：
<YOUR_CONFIG_CENTER> - 查询入口：
<YOUR_CONFIG_QUERY_ENDPOINT> - 鉴权：通过环境变量
CONFIG_QUERY_TOKEN（由进程环境提供，勿提交 Git）
What ships with it
1 file 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.
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 · 34 lines · 33 tokens per session scan A 281884a994c2
config-query is a skill published in the GitHub repository shanananana/deepticket (61 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 300 once invoked, about $0.0002 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.
Other skills, from other repositories
Incident Response Planner
Analyze an infrastructure incident alert and produce a structured response plan plus an executable on-call runbook. Use for incident, alert, on-call, and runbook requests.
incident-commander
Autonomous incident detection, root-cause analysis, and self-healing for Linux/Docker production environments. Activate when the user mentions: server down, high CPU, memory leak, disk full, service crash, deployment failure, alert firing, on-call page, or any infrastructure emergency. Also activates on scheduled…
dsh-k8s-diagnosis
Diagnose live Kubernetes failures (CrashLoopBackOff, OOMKilled, NodeNotReady, ImagePullBackOff, Network/CNI failures, HPA starvation, DNS failures, pending pods) with an evidence-first procedure: capture context, collect signals (events/status/logs), rank falsifiable hypotheses, verify one variable at a time, fix with…
design-incident-response
Use when creating or improving an incident response process for a production system or operational team.
sre-runbooks
Safe-by-default DevOps/SRE runbook automation for incident response, postmortems, on-call handovers, and operational troubleshooting. Implements Google SRE principles with agent-safe execution patterns including dry-run modes, human approval gates, and blast-radius limits.
kube-medic
Kubernetes Cluster Triage & Diagnostics — instant AI-powered incident triage via kubectl.