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 agents/gsd-build/get-shit-done/issue-trackergit clone --depth 1 https://github.com/gsd-build/get-shit-doneWrote 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/agents/gsd-build/get-shit-done/issue-tracker)<a href="https://agentmods.dev/agents/gsd-build/get-shit-done/issue-tracker"><img src="https://agentmods.dev/badge/agents/gsd-build/get-shit-done/issue-tracker.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.00000 | $0.00327 |
| Opus 5 | $0.00000 | $0.00163 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
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 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.
What it actually says
Issue tracker: GitHub
Issues for this repo live in GitHub Issues at gsd-build/get-shit-done.
Auth
Use the configured GitHub CLI session for this checkout. Do not require a
repo-local .envrc before running gh.
Conventions
- Create:
gh issue create --repo gsd-build/get-shit-done --title "..." --body "..." - Read:
gh issue view <number> --repo gsd-build/get-shit-done --comments - List:
gh issue list --repo gsd-build/get-shit-done --state open --json number,title,labels --jq '...' - Comment:
gh issue comment <number> --repo gsd-build/get-shit-done --body "..." - Label:
gh issue edit <number> --repo gsd-build/get-shit-done --add-label "..." --remove-label "..." - Close:
gh issue close <number> --repo gsd-build/get-shit-done --comment "..."
Always pass --repo gsd-build/get-shit-done explicitly — the local clone has multiple remotes and gh may resolve to the wrong one.
When a skill says "publish to the issue tracker"
Create a GitHub issue at gsd-build/get-shit-done.
When a skill says "fetch the relevant ticket"
Run gh issue view <number> --repo gsd-build/get-shit-done --comments.
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 · 28 lines · 0 tokens per session scan A dd48bb464451
issue-tracker is an agent published in the GitHub repository gsd-build/get-shit-done (64,606 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 327 tokens. 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 agents, from other repositories
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by {{COMMANDPREFIX}}new-project orchestrator.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.