agentmods.dev

issue-tracker

issue-tracker is an agent for coding agents from SSWConsulting/SSW.VerticalSliceArchitecture. It costs 0 tokens per session (1,126 once invoked), scanned A, a copy of issue-tracker, MIT.

An instruction guide for managing this repository's issues and product requirements documents through GitHub Issues, GitHub's built-in task and discussion system. It defines the commands and conventions for creating, viewing, commenting on, labeling, and closing issues.

In plain words
What is it for?
Use it to create or inspect issues, publish or update PRDs, add comments, apply triage labels, and close completed or rejected work.
Why use it?
It keeps issue-tracker work consistent and prevents using the wrong command or label. It also explains how the repository treats pull requests and triage states.

Agent

not rated 396 +1 29d ago A scan 0 tokens copy · 89% MIT
View the source file SSWConsulting/SSW.VerticalSliceArchitecture
Install

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.

agentmods
npx agentmods add agents/sswconsulting/ssw.verticalslicearchitecture/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/SSWConsulting/SSW.VerticalSliceArchitecture

Wrote 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.

agentmods badge for issue-tracker

README.md
[![agentmods](https://agentmods.dev/badge/agents/sswconsulting/ssw.verticalslicearchitecture/issue-tracker.svg)](https://agentmods.dev/agents/sswconsulting/ssw.verticalslicearchitecture/issue-tracker)
Your own site
<a href="https://agentmods.dev/agents/sswconsulting/ssw.verticalslicearchitecture/issue-tracker"><img src="https://agentmods.dev/badge/agents/sswconsulting/ssw.verticalslicearchitecture/issue-tracker.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,126 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01126
Opus 5 $0.00000 $0.00563
Sonnet 5 $0.00000 $0.00225
Haiku 4.5 $0.00000 $0.00113

Measured 5d ago against content hash 170f21aaeeb9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

issue-tracker 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 5d 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.

Origin

This is a copy

89% identical to issue-tracker — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

docs/agents/issue-tracker.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issue tracker: GitHub

Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.

Conventions

  • Create an issue: gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies.
  • Read an issue: gh issue view <number> --comments for a human-readable dump. --comments and --json are mutually exclusive (passing both silently drops --comments), so when you need to filter with jq, use gh issue view <number> --json number,title,body,labels,comments --jq '...' instead.
  • List issues: gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]' with appropriate --label and --state filters.
  • Comment on an issue: gh issue comment <number> --body "..."
  • Apply / remove labels: gh issue edit <number> --add-label "..." / --remove-label "..."
  • Close: gh issue close <number> --comment "..."

Infer the repo from git remote -v — gh does this automatically when run inside a clone.

Pull requests as a triage surface

PRs as a request surface: no. (Set to yes if this repo treats external PRs as feature requests; /triage reads this flag.)

When set to yes, PRs run through the same labels and states as issues, using the gh pr equivalents:

  • Read a PR: gh pr view <number> --comments and gh pr diff <number> for the diff.
  • List external PRs for triage: gh pr list --json has no authorAssociation field, so go through the REST API — gh api 'repos/{owner}/{repo}/pulls?state=open' --jq '.[] | select(.author_association as $a | ["CONTRIBUTOR","FIRST_TIME_CONTRIBUTOR","NONE"] | index($a)) | {number, title, user: .user.login, author_association}' — keeping only CONTRIBUTOR, FIRST_TIME_CONTRIBUTOR, or NONE (drop OWNER/MEMBER/COLLABORATOR).
  • Comment / label / close: gh pr comment, gh pr edit --add-label/--remove-label, gh pr close.

Read the full file on GitHub · 46 lines

Changes

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.

  1. 5d ago First seen · 46 lines · 0 tokens per session scan A 170f21aaeeb9

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository SSWConsulting/SSW.VerticalSliceArchitecture (396 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,126 tokens. A static security scan graded it A with 0 findings. It is 89% identical to issue-tracker, differing in 4 lines, and is treated as a copy.

Project managementasp-net-coredotnetef-coresoftware-architecturesswvertical-slice-architecture
Related

Other agents, from other repositories

cli

Use as the primary implementation agent for this .NET repository. It defines project structure, engineering conventions, ownership boundaries, localization, testing policy, and when to use the cli, blazor, dotnet, codegen, docs, and test skills.

AterDev/Perigon.CLI · 52 tokens

Reviewer

Use when reviewing Perigon.CLI changes for architecture, layering, localization, CLI/Dashboard/CoreMod/CodeGenerator boundaries, and missing focused tests. Read-only reviewer for implementation plans or diffs.

AterDev/Perigon.CLI · 42 tokens

write-tests-agent

Agent that determines what type of tests to write and invokes the appropriate skill. Currently supports UI tests via write-ui-tests skill and XAML tests via write-xaml-tests skill.

dotnet/maui · 39 tokens

looping

Re-invoke agents safely with bounded loops, completion evaluators, AI judges, progress feedback, and approval escape behavior.

managedcode/dotnet-skills · 24 tokens

planning-and-todos

Structure long-running agent work with todo and agent-mode providers, custom persistence, and plan-execute patterns.

managedcode/dotnet-skills · 21 tokens

frontend-engineer

Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.

fpindej/netrock · 39 tokens