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 navapbc/digital-service-orchestra --skill tickets-healthgit clone --depth 1 https://github.com/navapbc/digital-service-orchestraWrote 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/navapbc/digital-service-orchestra/tickets-health)<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/tickets-health"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/tickets-health/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/navapbc/digital-service-orchestra/tickets-health"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/tickets-health.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00126 | $0.01247 |
| Opus 5.5 | $0.00050 | $0.00499 |
| Sonnet 5.5 | $0.00025 | $0.00249 |
| Haiku 4.5 | $0.00013 | $0.00125 |
Grade A, and why
tickets-health 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 2mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Health Validation
When to Run
.claude/scripts/dso validate-issues.sh # Standard check
.claude/scripts/dso validate-issues.sh --verbose # Detailed output
Run after:
- Creating one or more new tasks
- Setting up dependencies between tasks
- Re-parenting tasks under epics
- When batch-creating tasks, run once after all tasks and initial relationships are created
Score Interpretation
| Score | Meaning | Action Required |
|---|---|---|
| 5 | Excellent | None - proceed with work |
| 4 | Good | Minor issues - fix if convenient |
| 3 | Fair | Must fix before continuing |
| 2 | Poor | Stop and fix - significant issues |
| 1 | Critical | Immediate action - blocking issues |
If Score < 5
- Review the issues reported by the script
- Ask the user for clarification before making significant changes to task descriptions, epic assignments, or dependency structures
- Prefer clarification over assumptions when:
- Task belongs to multiple possible epics
- Dependency direction is ambiguous
- Task description conflicts with epic goals
- After fixing issues, re-run
.claude/scripts/dso validate-issues.shto confirm score improves
Common Issues and Fixes
Orphaned Prefixed Task
Task has prefix (MC-, V-, A-, I-, L-, RR-) but no parent epic.
# Find the appropriate epic
.claude/scripts/dso ticket list --type=epic
# Assign parent (use add-note to record the epic association)
.claude/scripts/dso ticket comment <task-id> "Parent epic: <epic-id>"
Task Listed as Dependency Instead of Child
Epic depends on task, but task should be a child of epic.
# Remove incorrect dependency (.claude/scripts/dso ticket unlink <id1> <id2> to remove a link; note to user)
# Use .claude/scripts/dso ticket comment to record the correct parent association
.claude/scripts/dso ticket comment <task-id> "Parent epic: <epic-id> (was incorrectly set as dep)"
Empty Epic
Epic has no children or all children are closed.
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.
- 2mo ago First seen · 137 lines · 126 tokens per session scan A c4d72be23609
tickets-health is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 126 tokens to every session and 1,247 once invoked, about $0.0005 per session on Opus 5.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-09-03.
tickets-health compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| tickets-healthnavapbc/digital-service-orchestra | Skill | 6 | yesterday | Apache-2.0 | A | 126 | Claude Code |
| imagegenopenai/codex | Skill | 135k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 100k | today | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 316k | 7d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |