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 znlgis/my-opencode-deepseek-config --skill triagegit clone --depth 1 https://github.com/znlgis/my-opencode-deepseek-configWrote 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/znlgis/my-opencode-deepseek-config/triage)<a href="https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/triage"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/triage.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.00060 | $0.00342 |
| Opus 5 | $0.00030 | $0.00171 |
| Sonnet 5 | $0.00012 | $0.00068 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
triage 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.
What it actually says
Issue Triage
Sort a batch of issues by priority and type, and reflect that in labels and assignees — without changing the issues' substance.
When to use
A backlog needs routing: which are urgent, which are bugs vs features vs chores, who owns what.
Workflow
For exact gh command syntax, flags, and pagination, load the gh-cli skill.
- Pull:
gh issue list --state open --search "<filters>" --json number,title,labels(or--label <name>to scope to a label). Raise-Lfor large batches. - Classify: bucket each issue by type and severity from its title/body — not from assumptions.
- Apply:
gh issue edit <n> --add-label <type> --add-label <severity>and--add-assignee @meto claim ownership.
gh issue list --state open -L 50 --json number,title,labels,state
gh issue edit <n> --add-label bug --add-label P1 --add-assignee @me
Notes
- Never close an issue during triage — routing only.
- Preserve original title/body; add context via comments, not edits.
- Don't re-label something already correctly labeled.
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 · 37 lines · 60 tokens per session scan A 074b352b98de
triage is a skill published in the GitHub repository znlgis/my-opencode-deepseek-config (57 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 342 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-09-03.
Other skills, from other repositories
omc-plan
Strategic planning with optional interview workflow.
launch
Shipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the fog gate (an effort…
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
ask-navigator
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding, not building: it…
ultragoal
Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.