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/yokingma/one-search-mcp/issue-trackergit clone --depth 1 https://github.com/yokingma/one-search-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/yokingma/one-search-mcp/issue-tracker)<a href="https://agentmods.dev/agents/yokingma/one-search-mcp/issue-tracker"><img src="https://agentmods.dev/badge/agents/yokingma/one-search-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.00221 |
| Opus 5 | $0.00000 | $0.00111 |
| 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 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- issue-tracker — 95% identical, 1 lines differ
- issue-tracker — 95% identical, 1 lines differ
- issue-tracker — 86% identical, 5 lines differ
- issue-tracker — 84% identical, 7 lines differ
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) - Completion is recorded separately as
Resolution: completedso completion does not get mixed into triage state - 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.
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 · 21 lines · 0 tokens per session scan A 9fb0c442da65
issue-tracker is an agent published in the GitHub repository yokingma/one-search-mcp (139 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 221 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
release-manager
Owns the end-to-end modelcontextprotocol/csharp-sdk release process, orchestrating the prepare-release and publish-release skills (and the bump-version and breaking-changes skills they build on) across five stages: prepare (assess SemVer, bump the version, run ApiCompat/ApiDiff, review docs, draft release notes, open…
x402-profit-oracle
Audits this x402 repo as a commercial surface and raises revenue without breaking discovery, settlement, or the challenge cache. Read+write implement mode — may edit code and run tests; never spends and never touches keys. Use before building on a paid endpoint, changing a price, adding a product, or chasing a…
x402-merchant
Revenue side of x402 operations — builds seller payment requirements, verifies incoming payment payloads, and manages the Pro-tier/credit monetization flows. Use for anything about charging for services, verifying buyer payments, or pushing the group's net position toward ≥ 0.
x402-scout
Discovers and prices x402 paid services using ONLY free keyless tools. Use proactively whenever a task might need a paid API — scout finds it, prices it, and reports before anyone spends. Never pays.
x402-treasurer
The ONLY agent allowed to execute x402 payments via payandfetch on the keyed "vault" server instance. Use only after x402-warden has issued an APPROVE. Verifies settlement, records receipts, and refuses unapproved or unprobed payments.
x402-warden
Budget gatekeeper for x402 operations. MUST approve every payment before the treasurer executes. Tracks spend/revenue ledger, quota meta envelopes, and enforces caps. Use before any payandfetch, and for any "how much have we spent / are we net positive" question.