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/karbassi/slack-mcp/issue-trackergit clone --depth 1 https://github.com/karbassi/slack-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/karbassi/slack-mcp/issue-tracker)<a href="https://agentmods.dev/agents/karbassi/slack-mcp/issue-tracker"><img src="https://agentmods.dev/badge/agents/karbassi/slack-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.00283 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
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
83% identical to issue-tracker — 4 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: 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> --comments, filtering comments byjqand also fetching labels. - 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> --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 · 23 lines · 0 tokens per session scan A f0e138631d1f
issue-tracker is an agent published in the GitHub repository karbassi/slack-mcp (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 283 tokens. A static security scan graded it A with 0 findings. It is 83% identical to issue-tracker, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
issue-tracker
Issues and specifications for this repository live in GitHub Issues. Use the gh command-line tool for all operations.
builder
The builder is a local, scheduled Claude Code routine (cycle B of the delivery pipeline). It turns a fully-specified issue into a reviewed pull request, pausing once for human plan approval (Gate 1). It never merges. It is launched by scripts/builder-run.sh; its per-run instructions live in…
issue-approver
Approves an issue for workflow status transition. Launched by the issue-analysis supervisor skill once no open questions remain.
issue-updater
Updates a GitHub issue with refined content. Launched by the issue-analysis supervisor skill after the content has been agreed.
triage-labels
The engineering skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo, which follow the nitimini lifecycle vocabulary.
issue-tracker
Issues for this repo live as GitHub Issues, grouped by GitHub Milestones, modeled on the nitimini workflow. Use the gh CLI for all operations.