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 skills/saolalab/clawforce/ticket-managementnpx skills add saolalab/clawforce --skill ticket-managementgit clone --depth 1 https://github.com/saolalab/clawforceWrote 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/saolalab/clawforce/ticket-management)<a href="https://agentmods.dev/skills/saolalab/clawforce/ticket-management"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/ticket-management.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.00023 | $0.00566 |
| Opus 5 | $0.00012 | $0.00283 |
| Sonnet 5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
ticket-management 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 5d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Management
Ticket Lifecycle
New → Triaged → Assigned → In Progress → Resolved → Closed
↓
Escalated → [Engineering/Product/Other]
Triage Framework
Priority Levels
| Priority | Criteria | Response SLA | Resolution SLA |
|---|---|---|---|
| P0 - Critical | Service down, data loss, security breach | 15 minutes | 4 hours |
| P1 - High | Major feature broken, many users affected | 1 hour | 24 hours |
| P2 - Medium | Feature degraded, workaround available | 4 hours | 3 days |
| P3 - Low | Minor issue, cosmetic, feature request | 24 hours | 1 week |
Triage Checklist
- Identify the issue — What exactly is the customer reporting?
- Reproduce if possible — Can we see the same behavior?
- Check known issues — Is this a documented problem?
- Assess impact — How many users affected? Business impact?
- Assign priority — Based on impact and urgency
- Route appropriately — Self-resolve, escalate, or delegate
Ticket Template
## Summary
[One-line description]
## Customer
- Account: [customer name/ID]
- Contact: [email/channel]
- Segment: [enterprise/SMB/self-serve]
## Issue Details
- **Reported**: [timestamp]
- **Priority**: [P0/P1/P2/P3]
- **Category**: [bug/question/feature-request/account]
## Description
[Detailed description from customer]
## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Expected vs actual result]
## Investigation Notes
[Your findings]
## Resolution
[How it was resolved]
Escalation Criteria
Escalate when:
- You cannot reproduce or diagnose the issue
- The issue requires code changes
- Customer is threatening churn
- Security or data privacy is involved
- SLA is at risk
Metrics to Track
- First Response Time (FRT) — Time to first human response
- Time to Resolution (TTR) — Total time from ticket open to close
- First Contact Resolution (FCR) — % resolved in first interaction
- Customer Satisfaction (CSAT) — Post-resolution survey score
- Ticket Volume — Trends by category, priority, time
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.
- 5d ago First seen · 84 lines · 23 tokens per session scan A ff85999eea62
ticket-management is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 566 once invoked, about $0.0001 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
nemoclaw-maintainer-verify-stale
Verifies whether stale NVIDIA/NemoClaw bug reports still reproduce on the newest release tag. Use when maintainers ask to verify stale issues, reproduce old bugs on the newest release tag, or drain the bug backlog. Treats issue reproducers as untrusted, validates them on the reported release before a fixed verdict…
nemoclaw-maintainer-morning
Runs the morning maintainer standup for NemoClaw. Triages the backlog, determines the day's target version, labels selected items, surfaces stragglers from previous versions, and outputs the daily plan. Use at the start of the workday. Trigger keywords - morning, standup, start of day, daily plan, what are we shipping…
feature-matrix-parity
Update the OpenClaw and Hermes comparison columns of the ZeroClaw feature-and-support matrix. Use this skill when the user wants to refresh, fill, or verify parity data in docs/book/feature-matrix-parity.toml, add a new comparison row or section to the feature matrix, or re-walk the competitor repos for support…
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…
github-issue
File a structured GitHub issue for ZeroClaw interactively from Claude Code.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.