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 repo-workspacegit 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/repo-workspace)<a href="https://agentmods.dev/skills/shanananana/deepticket/repo-workspace"><img src="https://agentmods.dev/badge/skills/shanananana/deepticket/repo-workspace/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/shanananana/deepticket/repo-workspace"><img src="https://agentmods.dev/badge/skills/shanananana/deepticket/repo-workspace.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.00319 |
| Opus 5 | $0.00023 | $0.00160 |
| Sonnet 5 | $0.00009 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
repo-workspace 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 11d 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
只读代码工作区
何时需要读代码
- 需要看实现、调用链、配置定义 → 读
workspace/project/<repo-id>/ - 闲聊、概念解释、与具体仓库无关 → 不要打开 workspace
<repo-id> 来自 deepticket.yaml 的 knowledge.repos（例如 my-service）。
路径说明
| 路径 | 用途 |
|---|---|
workspace/project/<repo-id>/ |
Agent 只读分析入口（读这里） |
workspace/knowledge/<repo-id>/ |
Git 缓存；DeepTicket 启动或 UI「同步知识库」时更新 |
两者是同一仓库的两个视图，不是两个项目。优先读 workspace/project/，一般不要在对话里手动 git pull——需要最新代码时，请用户点「同步知识库」或告知已同步即可。
约束
- 只读：不修改、不提交
workspace/project下任何文件 - 不猜测用户本机其他路径（如
~/Projects/...），除非用户明确给出
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.
- 11d ago First seen · 28 lines · 47 tokens per session scan A 65f1fc2d3a45
repo-workspace is a skill published in the GitHub repository shanananana/deepticket (60 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 319 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.