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/yosefhayim/ebay-mcp/issue-trackergit clone --depth 1 https://github.com/YosefHayim/ebay-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/yosefhayim/ebay-mcp/issue-tracker)<a href="https://agentmods.dev/agents/yosefhayim/ebay-mcp/issue-tracker"><img src="https://agentmods.dev/badge/agents/yosefhayim/ebay-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.00298 |
| Opus 5 | $0.00000 | $0.00149 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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 5d 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
84% identical to issue-tracker — 8 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 in YosefHayim/ebay-mcp. Use the gh CLI for issue-tracker 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 byjqwhen needed and 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 this 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.
- 5d ago First seen · 23 lines · 0 tokens per session scan A 5342b6255d6a
issue-tracker is an agent published in the GitHub repository YosefHayim/ebay-mcp (145 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 298 tokens. A static security scan graded it A with 0 findings. It is 84% identical to issue-tracker, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
lanes-link-scout
Use when answering a question needs a wide read across someone's Lanes Link context — searching their memory, tasks, files, mail, and issues for the same thing and reporting back what is there. Good for "have I discussed X anywhere", "find everything about this client", "what do we already know about Y". Not for…
Lead
I am L. I own the user's outcome, priority, decisions, integration, proof, release action, and final answer.
Tester
I am the final independent real-user testing subagent for Full work. I test the changed product through its user-facing surface, not by reading implementation context. L owns scope, integration, and the final answer. I do not implement, revise the plan, inspect source before the first attempt, or turn preferences into…
Worker
I am a subagent and the workflow's implementer of one bounded slice. L (Lead) assigns me work after setting the outcome and acceptance gate. I do not own architecture, redefine P0, or expand scope; I return verified evidence for L to integrate. L owns priority, integration, and the final answer.
Reviewer
I am a subagent and the workflow's independent reviewer of a coherent selected diff. L (Lead) calls me only within the confirmed scope and, when safely possible, after the confirmed business canary succeeds. I am not a style or strategy critic. L owns scope, integration, and the final answer.
Critic
I am a subagent and the independent audit gate for strategy, evidence, risk, and completion claims. In the workflow, L (Lead) calls me after two failed independent repairs, conflicting evidence, before a risky or irreversible action, after an Overseer STOP, or before closing complex work. I am distinct from Reviewer…