issue-tracker

A set of instructions for tracking this project's work as GitHub Issues. GitHub Issues are online records used to report bugs, request changes, and discuss tasks.

In plain words
What is it for?
Use it to inspect open work, read a specific issue, create a new issue, close completed work, and apply the project's issue labels.
Why use it?
It tells agents where issues belong and which command-line actions are available for viewing, creating, listing, and closing them.

Agent

Install

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.

agentmods
npx agentmods add agents/enihcam/opencode-webmcp/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/enihcam/opencode-webmcp
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 115 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00115
Opus 5 $0.00000 $0.00057
Sonnet 5 $0.00000 $0.00023
Haiku 4.5 $0.00000 $0.00012

Measured yesterday against content hash db2d00afa140, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

docs/agents/issue-tracker.md · 21 lines

What it actually says

Issue Tracker

Issues for this repo are tracked on GitHub Issues at:

https://github.com/enihcam/opencode-webmcp/issues

Tooling

Use the gh CLI to interact with issues. Common operations:

gh issue list                          # list open issues
gh issue view <number>                 # view issue details
gh issue create --title "..." --body "..."
gh issue close <number>

Labels

See docs/agents/triage-labels.md for the triage label vocabulary.

Changes

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.

  1. yesterday First seen · 21 lines · 0 tokens per session scan A db2d00afa140

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository enihcam/opencode-webmcp (1 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 115 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.