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/samanhappy/mcphub/issue-trackergit clone --depth 1 https://github.com/samanhappy/mcphubWhat 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.00312 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 2d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- issue-tracker — 100% identical, 0 lines differ
- issue-tracker — 88% identical, 18 lines differ
- issue-tracker — 84% identical, 8 lines differ
- issue-tracker — 84% identical, 8 lines differ
- issue-tracker — 84% identical, 8 lines differ
- issue-tracker — 84% identical, 6 lines differ
- issue-tracker — 84% identical, 6 lines differ
- issue-tracker — 83% identical, 4 lines differ
What it actually says
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> --json number,title,body,labels,comments --jq '{number, title, body, labels: [.labels[].name], comments: [.comments[].body]}'. - 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--labeland--statefilters. - 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.
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> --json number,title,body,labels,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.
- 2d ago First seen · 23 lines · 0 tokens per session scan A dbfb230e88fe
issue-tracker is an agent published in the GitHub repository samanhappy/mcphub (2,356 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 312 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
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
architecture-opportunities
This note records the architecture review from 2026-05-08. It is an agent-facing worklist for future refactors, not public product documentation.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
accessibility-tester
Use this agent when you need comprehensive accessibility testing, WCAG compliance verification, or assessment of assistive technology support.
backend-test-engineer
Backend test engineer for Arthur MCP. Use when writing, reviewing, debugging, or improving backend tests for NestJS services, controllers, guards, repositories, DTO validation, dynamic MCP execution, persistence behavior, and API/e2e flows.
build-engineer
Use this agent when you need to optimize build performance, reduce compilation times, or scale build systems across growing teams.