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/serac-labs/serac/problem-managementnpx skills add serac-labs/serac --skill problem-managementgit clone --depth 1 https://github.com/serac-labs/seracWrote 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/serac-labs/serac/problem-management)<a href="https://agentmods.dev/skills/serac-labs/serac/problem-management"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/problem-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.00053 | $0.03525 |
| Opus 5 | $0.00026 | $0.01762 |
| Sonnet 5 | $0.00011 | $0.00705 |
| Haiku 4.5 | $0.00005 | $0.00352 |
Grade A, and why
problem-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 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 — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Management for ServiceNow
Problem Management identifies root causes of incidents and implements permanent solutions.
Problem Lifecycle
New (1)
↓
Assess (2)
↓
Root Cause Analysis (3)
↓
Fix in Progress (4) ← Known Error Database
↓
Resolved (5)
↓
Closed (6)
Cancelled (7) ← Can occur from any state
Key Tables
| Table | Purpose |
|---|---|
problem |
Problem records |
problem_task |
Problem investigation tasks |
known_error |
Known Error Database (KEDB) |
incident |
Related incidents |
Creating Problems (ES5)
Create Problem from Incidents
// Create problem from multiple incidents (ES5 ONLY!)
function createProblemFromIncidents(incidentSysIds, problemData) {
// Create problem
var problem = new GlideRecord("problem")
problem.initialize()
problem.setValue("short_description", problemData.title)
problem.setValue("description", problemData.description)
problem.setValue("category", problemData.category)
problem.setValue("subcategory", problemData.subcategory)
// Set impact based on related incidents
var highestImpact = 3
for (var i = 0; i < incidentSysIds.length; i++) {
var incident = new GlideRecord("incident")
if (incident.get(incidentSysIds[i])) {
var incImpact = parseInt(incident.getValue("impact"), 10)
if (incImpact < highestImpact) {
highestImpact = incImpact
}
}
}
problem.setValue("impact", highestImpact)
problem.setValue("urgency", highestImpact)
// Assignment
if (problemData.assignmentGroup) {
problem.setValue("assignment_group", problemData.assignmentGroup)
}
// Affected CI
if (problemData.cmdb_ci) {
problem.setValue("cmdb_ci", problemData.cmdb_ci)
}
var problemSysId = problem.insert()
// Link incidents to problem
for (var j = 0; j < incidentSysIds.length; j++) {
var incidentToLink = new GlideRecord("incident")
if (incidentToLink.get(incidentSysIds[j])) {
incidentToLink.setValue("problem_id", problemSysId)
incidentToLink.work_notes = "Linked to Problem: " + problem.getValue("number")
incidentToLink.update()
}
}
return {
sys_id: problemSysId,
number: problem.getValue("number"),
}
}
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 · 540 lines · 53 tokens per session scan A cac824343684
problem-management is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 9d ago), licensed Apache-2.0. It adds 53 tokens to every session and 3,525 once invoked, about $0.0003 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
daily-standup
Generates daily standup reports from accomplishments, plans, and blockers.
servicenow-ticket
Create a ServiceNow incident via the Table API. Requires SERVICENOWINSTANCE, SERVICENOWUSER, and SERVICENOWPASSWORD environment variables on the server. Trigger on: create a ServiceNow incident, raise an ITSM ticket, log an incident.
development-orchestration
Compose Herdr tools and domain Skills into dependency-aware development lanes with explicit ownership, validation, and safe worktree/workspace reclamation.
queue
Use when the user says "queue", "/queue", "add to the backlog", "capture this", or drops a thought/idea/question mid-arc that should NOT derail the current work. Appends the item to docs/BACKLOG.md with a date and moves on. With no argument, shows the open backlog. This is capture, not analysis - the point is to not…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
github
GitHub CLI (gh) for repository management, issues, pull requests, releases, workflows, search, gists, and API access. Use when the user asks about any GitHub operation — creating repos, forking, cloning, PR workflows, issue triage, CI/CD runs, code search, release management, or direct API calls. Keywords: github, gh…