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 to-ticketsgit 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/to-tickets)<a href="https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/to-tickets"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/to-tickets/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/znlgis/my-opencode-deepseek-config/to-tickets"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/to-tickets.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.00060 | $0.00374 |
| Opus 5 | $0.00030 | $0.00187 |
| Sonnet 5 | $0.00012 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
to-tickets 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 7d 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
To Tickets
Turn a written spec or plan into a set of trackable issues. One issue per unit of work, each verifiable on its own.
When to use
A spec/plan exists and needs to become actionable, reviewable issues — not when the work is a single step you can just do inline.
How to break down
- One issue = one unit that can be completed and verified independently.
- Every issue carries acceptance criteria (the observable "done" condition).
- Keep issues small enough to finish and review in one session; split anything that would outlive one.
Creating issues with gh
For exact gh command syntax, flags, and pagination, load the gh-cli skill.
gh issue create --title "<summary>" --body "<body>" --assignee @me
--bodyholds the scope, acceptance criteria, and dependency notes.- Use
--type Task(orBug/Feature) when the repo uses issue types. - Batch-create from a plan: one
gh issue createper ticket.
Notes
- Granularity: aim for units a single agent session can finish — not one giant issue, not twenty trivial ones.
- Dependencies: annotate blocking relationships (e.g. "blocked by #12") rather than assuming order.
- Don't create issues for work you're about to do inline — tickets are for tracking work across sessions or humans.
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.
- 7d ago First seen · 43 lines · 60 tokens per session scan A cb8710c2d084
to-tickets is a skill published in the GitHub repository znlgis/my-opencode-deepseek-config (58 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 374 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
git-workflow
Branching strategies, conventional commits, PR templates, and merge vs rebase guidance. Activate when starting features, creating PRs, or managing releases.
wrap-phase
Wraps up a development phase by cleaning AGENTSYNC.md, summarizing work, and committing changes.
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
batonq-pr-runner
Implements a batonq task end-to-end and opens a pull request. Adds git discipline, branch naming, conventional-commit enforcement, and PR-body conventions on top of batonq-worker. Use when a task explicitly requires a PR (not a direct commit to main) — e.g., tasks running in fire-and-forget mode against repos with…
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.