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 lugassawan/swe-workbench --skill ticket-contextgit clone --depth 1 https://github.com/lugassawan/swe-workbenchWrote 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/lugassawan/swe-workbench/ticket-context)<a href="https://agentmods.dev/skills/lugassawan/swe-workbench/ticket-context"><img src="https://agentmods.dev/badge/skills/lugassawan/swe-workbench/ticket-context/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/lugassawan/swe-workbench/ticket-context"><img src="https://agentmods.dev/badge/skills/lugassawan/swe-workbench/ticket-context.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.00048 | $0.01370 |
| Opus 5.5 | $0.00019 | $0.00548 |
| Sonnet 5.5 | $0.00010 | $0.00274 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
ticket-context 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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to invoke
Auto-loads when the caller references:
- Jira key:
[A-Z][A-Z0-9]+-\d+— e.g.PROJ-123. A bare key routes to Jira by default; see the Linear adapter's Trigger field for the availability tiebreak that reroutes it when only a Linear MCP tool is reachable. - Atlassian Jira URL:
*.atlassian.net/browse/<KEY>. - Confluence URL:
*.atlassian.net/wiki/spaces/...or*.atlassian.net/wiki/pages/.... - Linear URL:
linear.app/<workspace>/issue/<TEAM-N>— routes here unconditionally. - GitHub issue/PR URL:
github.com/<owner>/<repo>/(issues|pull)/\d+. - GitHub short ref:
#\d+with current-repo context.
If no reference is present, exit cleanly.
Adapters
Jira issue
- Trigger: Jira key (
[A-Z][A-Z0-9]+-\d+) or Atlassian Jira URL (*.atlassian.net/browse/<KEY>). A bare key routes here unless the Linear adapter's availability tiebreak applies. - Fetch: First fetch in session: call
mcp__atlassian__getAccessibleAtlassianResourcesforcloudId(cache for session). Thenmcp__atlassian__getJiraIssuewith the key. - Extract → block fields: summary, issuetype, status, priority, description → Title/Type-Status/Summary; labels, components, acceptance-criteria (check description body if no dedicated field) → Acceptance criteria; linked issues via
mcp__atlassian__getJiraIssueRemoteIssueLinks→ Linked references; last 5 comments → Recent activity. - Degrade: If Atlassian MCP unavailable, try
mcp__atlassian__fetchwith raw URL; if still failing, emitticket-context: Atlassian MCP unavailable; proceeding without context.On auth error, surface the raw error; never fabricate. On empty/404, say so; do not guess.
Confluence page
- Trigger: Confluence URL (
*.atlassian.net/wiki/spaces/...or*.atlassian.net/wiki/pages/...). - Fetch: Extract page ID from
/pages/<ID>in the URL. Usemcp__atlassian__getConfluencePage; fall back tomcp__atlassian__fetchwith raw URL if the ID is unclear. - Extract → block fields: title → Title; version, body (rendered text) → Summary; footer comments via
mcp__atlassian__getConfluencePageFooterComments(if any) → Recent activity. - Degrade: If Atlassian MCP unavailable, try
mcp__atlassian__fetchwith raw URL; if still failing, emitticket-context: Atlassian MCP unavailable; proceeding without context.On auth error, surface the raw error; never fabricate. On empty/404, say so; do not guess.
What ships with it
1 file 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.
- 1mo ago First seen · 68 lines · 48 tokens per session scan A 344cdf5e72ad
ticket-context is a skill published in the GitHub repository lugassawan/swe-workbench (3 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 1,370 once invoked, about $0.0002 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.
Other skills, from other repositories
requirement-forge-refiner
Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution…
state-scanner
A project-status scanner and workflow recommender, described in Chinese, for guiding development work through a ten-step process. It gathers information about Git, progress, specifications, audits, and changes, then proposes a workflow for user approval.
state-scanner
A project-status checker that examines repository changes and related workflow records, then suggests what to do next. It can pass the chosen workflow to another tool after the user confirms it.
helper
A workflow helper for archiving completed OpenSpec changes into an archive directory and checking that the archived result is in the expected place. OpenSpec is a specification-change workflow.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".