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/open-bio/openbio-comfy-mcp/issue-trackergit clone --depth 1 https://github.com/Open-Bio/openbio-comfy-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/open-bio/openbio-comfy-mcp/issue-tracker)<a href="https://agentmods.dev/agents/open-bio/openbio-comfy-mcp/issue-tracker"><img src="https://agentmods.dev/badge/agents/open-bio/openbio-comfy-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.1 | $0.00000 | $0.00261 |
| Opus 5 | $0.00000 | $0.00130 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
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.
What it actually says
Issue tracker: Local Markdown
Issues and specs for this repo live as Markdown files in .scratch/.
Conventions
- One feature per directory:
.scratch/<feature-slug>/ - The spec is
.scratch/<feature-slug>/spec.md - Implementation issues are one file per ticket at
.scratch/<feature-slug>/issues/<NN>-<slug>.md - Ticket numbers start at
01 - Comments and conversation history append under a
## Commentsheading
Publishing to the issue tracker
Create a new file under .scratch/<feature-slug>/, creating the directory when needed.
Fetching a ticket
Read the referenced file directly. The user normally provides its path or issue number.
Wayfinding operations
- Map:
.scratch/<effort>/map.md - Child ticket:
.scratch/<effort>/issues/<NN>-<slug>.md - Ticket type:
Type: research|prototype|grilling|task - Ticket state:
Status: claimed|resolved - Dependencies:
Blocked by: <NN>, <NN> - Claim by setting
Status: claimedbefore starting - Resolve by adding an
## Answer, settingStatus: resolved, and recording the result inmap.md
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 · 30 lines · 0 tokens per session scan A 2b2bf510a178
issue-tracker is an agent published in the GitHub repository Open-Bio/openbio-comfy-mcp (0 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 261 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-31.
Other agents, from other repositories
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
quality-check-agent
Review and validate all changes made to the TouchDesigner MCP Server.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
audit
🔬 [5維度審計] 深度程式碼審計 — 架構合規 + 安全性 + 品質 + 測試覆蓋 + 文檔同步。.
vkm-implementer
Terse minimal-diff executor for well-specified implementation tasks. Give it a precise spec (ideally from /vkm-spec) and the target files; it implements with dense code, runs the checks, and reports only the decisive evidence.
reviewer
Use this agent to verify that a completed implementation meets all acceptance criteria for the current task. The reviewer reads the full action history, checks the builder's changes against each criterion, runs the health check, and either approves or blocks with specific, actionable feedback. Invoke only after the…