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/lexwdex/opencode-graphagent/issue-trackergit clone --depth 1 https://github.com/LeXwDeX/OpenCode-GraphAgentWhat 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.00640 |
| Opus 5 | $0.00000 | $0.00320 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 or remove labels:
gh issue edit <number> --add-label "..."or--remove-label "..." - Close:
gh issue close <number> --comment "..."
Infer the repository from git remote -v; gh does this automatically when run inside this clone.
Pull requests as a triage surface
PRs as a request surface: no.
Pull requests are delivery artifacts, not incoming requests. /triage does not include them in its queue.
GitHub shares one number space across issues and PRs. Resolve an ambiguous #42 with gh pr view 42, then fall back to gh issue view 42.
Skill operations
- 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. - Use GitHub's native blocking relationships when available. If unavailable, put
Blocked by: #<n>at the top of the issue body.
Wayfinding operations
Used by /wayfinder. The map is one issue with child issues as tickets.
- Map: an issue labelled
wayfinder:map, holding Notes, Decisions-so-far, and Fog. - Child ticket: a GitHub sub-issue labelled
wayfinder:<type>where type isresearch,prototype,grilling, ortask. If sub-issues are unavailable, link it from a task list in the map and putPart of #<map>at the top of the child body. - Blocking: prefer GitHub native issue dependencies. Use the blocker's numeric database ID with the dependencies API, not its issue number or node ID. Fall back to a
Blocked by:line only when native dependencies are unavailable. - Frontier query: select the first open, unassigned child in map order whose blockers are all closed.
- Claim:
gh issue edit <n> --add-assignee @meis the working session's first write. - Resolve: comment with the decision, close the child, and add its context pointer to the map's Decisions-so-far.
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.
- yesterday First seen · 40 lines · 0 tokens per session scan A f59f45e65184
issue-tracker is an agent published in the GitHub repository LeXwDeX/OpenCode-GraphAgent (111 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 640 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
triage-labels
Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").
lead
Use this agent to orchestrate a full task from the harness backlog: decompose it into a plan, delegate to explorer, builder, and reviewer in sequence, and close the session correctly. Invoke when starting a new work session, picking up a pending task, or when another agent reports a blocker that requires…
feature-planner
Epics, user stories, prioritization, backlog management.
issue-tracker
Issues and specs (you may know a spec as a PRD) for this repo live as markdown files in .scratch/.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.