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 arozumenko/sdlc-skills --skill issue-trackinggit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote 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/arozumenko/sdlc-skills/issue-tracking)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/issue-tracking"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/issue-tracking/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/arozumenko/sdlc-skills/issue-tracking"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/issue-tracking.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.00059 | $0.02199 |
| Opus 5 | $0.00030 | $0.01099 |
| Sonnet 5 | $0.00012 | $0.00440 |
| Haiku 4.5 | $0.00006 | $0.00220 |
Grade A, and why
issue-tracking 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 9d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Tracking
Create, query, comment on, and close tickets on whatever tracker the
project actually uses. This skill is tracker-aware — the same
operation lands in the right system because the dispatch reads
.agents/profile.md.
Step 0 — Read the destination from profile.md
Before any command, open .agents/profile.md § Project systems §
Issue tracker. Scout's Step 0.7 records one of:
| Value (profile.md) | Default tooling |
|---|---|
github-issues (default) |
gh CLI |
gitlab-issues |
glab CLI |
jira |
Atlassian MCP (create / comment / transition); body must be in ADF |
azure-devops |
Azure DevOps MCP (az boards as a fallback) |
linear |
Linear CLI (linear) or Linear MCP |
Unconfirmed |
Default to gh; surface the gap to the operator so scout can fill the field |
On restrictive hosts (e.g. Copilot CLI), scout's Step 6.8 has already
wired the matching CLI/MCP into the calling agent's tools:
whitelist based on what's actually installed. If the named tracker
has no wired tool, stop and escalate rather than silently falling
back — the right ticket in the wrong tracker is worse than no ticket.
Body templates
Body shapes are tracker-agnostic markdown — they live in
references/templates.md and are reused
across all trackers. Pick:
- Bug Report — defect filing (severity, environment, steps,
expected, actual, evidence, frequency, workaround); for
lightweight clarifications, use the same template at
[INFO]severity - Task — implementation task under an epic
- Epic — multi-task feature umbrella
Render the markdown body, then hand it to the tracker-specific command below. Jira / Azure DevOps require ADF (Atlassian Document Format) rather than markdown — convert via whatever ADF-authoring capability your agent has wired.
File a defect
Standard flow when the caller is filing a new defect:
- Read
.agents/profile.md§ Project systems § Issue tracker (see Step 0 above) and § Bug filing — the latter records:- Bug filing style:
github-issue(standalone) /story-subtask(sub-task under a parent story; Jira / ADO only) /separate-ticket(filed into a dedicated QA/bugs project) - Bug filing target: when style is
separate-ticket, the destination project/board key
- Bug filing style:
- Fill the Bug Report template from
references/templates.md. - Open the ticket via the tracker's create command (see Create
issue below). For
story-subtask, the caller is responsible for providing the parent story ID; pass it as the parent when invoking the tracker's create command. Forseparate-ticket, target the project named in § Bug filing target. - Return the ticket ID and URL to the caller. What the caller does with that ID (note in an AFS, attach to a test, link in a PR body) is caller policy, not this skill's concern.
What ships with it
2 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.
- 9d ago First seen · 232 lines · 59 tokens per session scan A 14a099598d07
issue-tracking is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 2,199 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-08-30.
Other skills, from other repositories
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.