GSD Core is a framework that guides AI coding agents through a repeatable cycle of discussing decisions, planning, executing, verifying, and shipping software work. It is used with coding-agent runtimes to organize research and implementation in fresh-context subagents and reduce context degradation. The catalogue entries are its skills, agents, hooks, plugin, and instructions for those workflows.
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/open-gsd/gsd-core/triage-labelsgit clone --depth 1 https://github.com/open-gsd/gsd-coreWrote 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/open-gsd/gsd-core/triage-labels)<a href="https://agentmods.dev/agents/open-gsd/gsd-core/triage-labels"><img src="https://agentmods.dev/badge/agents/open-gsd/gsd-core/triage-labels.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.1 | $0.00000 | $0.01297 |
| Opus 5 | $0.00000 | $0.00648 |
| Sonnet 5 | $0.00000 | $0.00259 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
triage-labels 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 6d 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.
Triage Labels
Maps the five canonical triage roles to the actual label strings in open-gsd/gsd-core.
| Canonical role | Label in this repo | Notes |
|---|---|---|
needs-triage |
needs-triage |
Auto-applied by GitHub Action on every new issue |
needs-info |
needs-reproduction |
Waiting on reporter — cannot reproduce, more info required |
ready-for-agent |
confirmed-bug |
Bug verified + fully specified — AFK agent can pick up. This is the fix gate (RULESET.CONTRIB.CLASSIFY.fix); bug-remediation workflows scope on it. |
ready-for-human |
approved-enhancement / approved-feature |
Enhancement/feature approved by maintainer — human codes it |
wontfix |
wontfix |
Will not be actioned |
possible-duplicate |
possible-duplicate |
Applied by the Duplicate check workflow when a new issue's title closely matches existing open issues. The reporter (or a maintainer) replies justifying why it is not a duplicate within 24h, or the Duplicate auto-close sweep closes it. A reply clears this label and applies needs-maintainer-review for human adjudication. React 👎 to the bot comment to veto auto-close. |
needs-version |
needs-version |
Applied by the Version gate workflow when a bug report is auto-closed for missing a valid GSD Version. Edit the issue to add the version and reopen it. |
version-exempt |
version-exempt |
Maintainer-only opt-out label. Prevents the Version gate from closing an issue where a version genuinely does not apply. |
Notes on this repo's label model
confirmed-bugis the AFK-agent-ready signal for bugs. It means "verified reproducible bug" and is the gate the fix workflow requires before any code is written. Apply it (in addition tobug) when triage reproduces/verifies a bug. The legacyconfirmedlabel ("bug verified to exist") is retained only for back-compat in the duplicate-sweep exempt list — useconfirmed-bugfor new triage.- For enhancements and features, maintainer approval is
approved-enhancement/approved-featurerespectively. A contributor (human or agent) may not write code until one of these is applied. - There is no separate "ready-for-human" vs "ready-for-agent" distinction for enhancements — both flow through the same
approved-*labels. If the work requires human judgment (design decisions, external access), note it in the issue body. needs-triageis removed when any other state label is applied.needs-reproductionis used instead of the genericneeds-info— be specific in triage comments about what reproduction steps or information are missing.
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.
- 6d ago First seen · 43 lines · 0 tokens per session scan A a353b3b6e53b
triage-labels is an agent published in the GitHub repository open-gsd/gsd-core (9,125 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,297 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
security
OWASP security audit, dependency risks, and secrets detection.
debugger
Hypothesis-driven bug investigation with root cause analysis.
javascript-pro
Modern JavaScript specialist for browser, Node.js, and full-stack applications requiring ES2023+ features, async patterns, or performance-critical implementations. Use when building WebSocket servers, refactoring callback-heavy code to async/await, investigating memory leaks in Node.js, scaffolding ES module libraries…
typescript-pro
TypeScript specialist for advanced type system patterns, complex generics, type-level programming, and end-to-end type safety across full-stack applications. Use when designing type-first APIs, creating branded types for domain modeling, building generic utilities, implementing discriminated unions for state machines…
doc-writer
Documentation generation from code — API docs, inline comments, READMEs.
git-ops
Conflict resolution, rebase strategy, PR preparation, and changelog generation.