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 agentmods add skills/baleen37/bstack/twg-jiranpx skills add baleen37/bstack --skill twg-jiragit clone --depth 1 https://github.com/baleen37/bstackWrote 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/baleen37/bstack/twg-jira)<a href="https://agentmods.dev/skills/baleen37/bstack/twg-jira"><img src="https://agentmods.dev/badge/skills/baleen37/bstack/twg-jira.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00503 |
| Opus 5 | $0.00009 | $0.00251 |
| Sonnet 5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
twg-jira 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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
twg-jira
Use with the root twg skill whenever Jira is the source of truth. This skill covers Jira only.
Routing
| Intent | Command |
|---|---|
| Jira-only fuzzy text | twg jira workitem search "text" --limit 20 |
| Explicit JQL | twg jira workitem query --jql 'project = PROJ ORDER BY updated DESC' |
| Semantic Jira discovery | twg search "text" --app jira |
| Known issue read | twg jira workitem get PROJ-123 |
| Create | twg jira workitem create ... --yes after metadata/read confirmation and explicit user approval |
| Comments | twg jira workitem comment create/update ... after reading current state |
Use twg help describe "<command path>" for exact command grammar. Issue keys are positional for twg jira workitem get; do not guess flags, fields, or transition names.
Search results are candidate anchors. Use a native twg jira workitem get PROJ-123 read to confirm final fields, status, comments, and URLs.
Output boundaries
- Use bounded, human-readable output by default for searches and reads.
- Limit result counts with
--limitor the command's appropriate range before expanding a query. - Use
--output jsononly when filtering results or collecting machine-readable evidence requires it.
Safe mutations
- Read current state before every create, update, comment, or transition.
- Before create or update, inspect the required field metadata and provide returned custom field IDs rather than guessed display names.
- Before a transition, discover available transitions rather than guessing one.
- For every state-changing operation, including create, update, comment, transition, link, and any similar mutation, first show the exact change, target, and expected impact to the user.
- Execute a state-changing operation only after the user explicitly approves the shown mutation; do not execute it before approval.
- Apply this rule whether or not --yes is present. The
--yesflag never substitutes for explicit user approval. - Reads and searches remain allowed without this approval.
- Verify a completed mutation with a native issue read and report the resulting issue key and URL.
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 · 43 lines · 17 tokens per session scan A 6ca741faff24
twg-jira is a skill published in the GitHub repository baleen37/bstack (4 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 503 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…