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/starwind-ui/starwind-ui-mcp/issue-trackergit clone --depth 1 https://github.com/starwind-ui/starwind-ui-mcpWrote 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/starwind-ui/starwind-ui-mcp/issue-tracker)<a href="https://agentmods.dev/agents/starwind-ui/starwind-ui-mcp/issue-tracker"><img src="https://agentmods.dev/badge/agents/starwind-ui/starwind-ui-mcp/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.00218 |
| Opus 5 | $0.00000 | $0.00109 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
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.
This is a copy
86% identical to issue-tracker — 5 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.
What it actually says
Issue tracker: Local Markdown
Issues and PRDs for this repo live as markdown files in .scratch/.
Conventions
- One feature per directory:
.scratch/<feature-slug>/ - The PRD is
.scratch/<feature-slug>/PRD.md - Implementation issues are
.scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from01 - Triage state is recorded as a
Status:line near the top of each issue file (seetriage-labels.mdfor the role strings) - Comments and conversation history append to the bottom of the file under a
## Commentsheading
When a skill says "publish to the issue tracker"
Create a new file under .scratch/<feature-slug>/ (creating the directory if needed).
When a skill says "fetch the relevant ticket"
Read the file at the referenced path. The user will normally pass the path or the issue number directly.
Pull requests
External pull requests are not a triage surface for the local markdown tracker.
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 · 24 lines · 0 tokens per session scan A 9dc7d91abdd1
issue-tracker is an agent published in the GitHub repository starwind-ui/starwind-ui-mcp (35 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 218 tokens. A static security scan graded it A with 0 findings. It is 86% identical to issue-tracker, differing in 5 lines, and is treated as a copy.
Other agents, from other repositories
planner
PROVE Plan stage. Use to turn a request into an approved plan — question, discover, specify, plan — writing only to the change packet, never product code. Dispatch first, before any building. Do not use to edit code, run commands, or decide ship/block.
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.
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.
webkit-adoption-auditor
Measures how much of an app already renders through @aziontech/webkit versus hand-rolled UI, and produces a prioritized backlog of custom components that have a webkit equivalent to adopt.
captain
Shipshape Captain: specification author, voyage lead, and outbound liaison. Use for voyage planning and spec-driven dispatch.
issue-tracker
Issues for this repo live in GitHub Issues on danhnm1203/scrollytelling, managed with the gh CLI.