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/shaps80/swiftuibackports/issue-trackergit clone --depth 1 https://github.com/shaps80/SwiftUIBackportsWrote 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/shaps80/swiftuibackports/issue-tracker)<a href="https://agentmods.dev/agents/shaps80/swiftuibackports/issue-tracker"><img src="https://agentmods.dev/badge/agents/shaps80/swiftuibackports/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.00266 |
| Opus 5 | $0.00000 | $0.00133 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00027 |
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 and PRDs for this repo live as GitHub issues in shaps80/SwiftUIBackports. Use the gh CLI for operations when connector tools are not already handling GitHub work.
Conventions
- Create an issue:
gh issue create --title "..." --body "..." - Read an issue:
gh issue view <number> --comments - List issues:
gh issue list --state open --json number,title,body,labels,comments - Comment on an issue:
gh issue comment <number> --body "..." - Apply or remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Close an issue:
gh issue close <number> --comment "..."
Infer the repo from git remote -v; gh does this automatically inside the clone.
When A Skill Says "Publish To The Issue Tracker"
Create a GitHub issue.
When A Skill Says "Fetch The Relevant Ticket"
Run gh issue view <number> --comments.
Release Labels
Pull requests must have exactly one of:
release:majorrelease:minor
The GitHub Actions release label check fails if neither or both are present.
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 · 32 lines · 0 tokens per session scan A 875ed94b6056
issue-tracker is an agent published in the GitHub repository shaps80/SwiftUIBackports (1,088 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 266 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
i18n
Hermex ships one String Catalog, HermesMobile/Resources/Localizable.xcstrings, included in the app, widget, and share-extension targets. Every user-facing literal is already externalized (String(localized:) / LocalizedStringKey), so adding a language is normally translation-only — no Swift edits.
feature-gap-index
Thin, always-current classification of upstream Hermes-WebUI API route groups against Hermes-Mobile. This file replaces an earlier 1,400-line per-endpoint catalog, which mixed durable judgment (priority, defer/skip decisions, safety notes) with volatile detail (exact JSON shapes, handler names) that rotted between…
tooling-runner
Haiku runner for TMDb build/test commands — executes exactly one make target (or its xcode-tools MCP equivalent), writes the full output to a .build/last-.log file, and returns only a concise pass/fail + failures-as-file:line summary. Spawned by the /build, /build-for-testing, /test, and /integration-test skills; not…
check-diagnoser
No-fix diagnoser for one failing PR status check on the TMDb repo — runs the routed diagnosis skill (/diagnose-ci-failure or /diagnose-integration-failure) and returns only its three-section Summary / Likely cause / Suggested fix result, never raw logs; it reports, never applies. Spawned by /fix-pr-checks (directly…
omp
Install Remarc's public OMP plugins, verify the MCP connection, and pair a session for instant comment delivery.
i18n
Multiplex ships English (source), Traditional Chinese (zh-Hant, Taiwan wording) and Japanese (ja). Decisions below were settled 2026-08-18; do not re-litigate without new facts.