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 darellchua2/opencode-config-template --skill ticket-creation-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/ticket-creation-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/ticket-creation-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/ticket-creation-skill/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/darellchua2/opencode-config-template/ticket-creation-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/ticket-creation-skill.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.00063 | $0.04223 |
| Opus 5.5 | $0.00025 | $0.01689 |
| Sonnet 5.5 | $0.00013 | $0.00845 |
| Haiku 4.5 | $0.00006 | $0.00422 |
Grade A, and why
ticket-creation-skill scanned grade A with 1 finding 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 28d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The `atlassian` MCP server is **disabled by default**. Policy per `jira-git-integration-skill` §MCP Availability Guard. REST fallback for this skill: API token + `curl -u email:token` against `https://<site>.atlassian.ne How it starts
The opening of the file, as written. The whole thing — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Renamed from ticket-plan-workflow-skill — planning/execution steps moved
to worktree-pipeline-skill (invoked via /run-worktree-pipeline).
What I do
I create well-structured tickets on GitHub Issues or JIRA — nothing else:
- Detect Platform: GitHub Issues or JIRA based on user input and project setup
- Intake: classify variant (bug | feature | task), collect its required fields, validate, preview — mirroring a human filling the issue form
- Determine Ticket Scope: single ticket vs parent with sub-issues/subtasks
- Create Ticket: GitHub CLI (
gh) or Atlassian MCP with appropriate labels/type
Branch creation, PLAN generation, and execution belong to
worktree-pipeline-skill (/run-worktree-pipeline). To go end-to-end,
create the ticket here, then run the pipeline against its ref.
Framework Skills Used
| Skill | Purpose | Used In |
|---|---|---|
git-issue-labeler |
GitHub label assessment and assignment | Step 4 (GitHub) |
jira-ticket-labeler |
JIRA issue type and priority classification | Step 4 (JIRA) |
When to use me
- Starting a new development task tracked in GitHub Issues or JIRA
- You want a standardized, well-structured ticket as the artifact
ghavailable (GitHub) oratlassianMCP enabled (JIRA — see guard below)
Prerequisites
GitHub Issues
- GitHub CLI (
gh) installed and authenticated (gh auth statusvalid). Ifcommand -v ghfails, loadgh-cli-setup-skill(install + auth), then continue instead of erroring. - Git repository with GitHub remote; write access to repository
JIRA
- Active Atlassian/JIRA account with project access
atlassianMCP server enabled in this session (opt-in — see MCP Availability Guard)
MCP Availability Guard (JIRA steps)
The atlassian MCP server is disabled by default. Policy per jira-git-integration-skill §MCP Availability Guard. REST fallback for this skill: API token + curl -u email:token against https://<site>.atlassian.net. Degrade: run the GitHub-only flow, report JIRA steps as skipped.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 28d ago Changed · +2 lines 83bcca2f7a1b
- 29d ago Changed · +63 lines 872aca6ab8e7
- 1mo ago Changed · -11 lines 54ca30a8aa00
- 1mo ago Changed · +74 lines 8334d067ddc0
- 1mo ago Changed a74efcf7b0a7
- 1mo ago First seen · 262 lines · 63 tokens per session scan A 0a49de89b520
ticket-creation-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 28d ago), licensed Apache-2.0. It adds 63 tokens to every session and 4,223 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.
Other skills, from other repositories
git-ship
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.