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/alvinunreal/oh-my-opencode-slim/issue-trackergit clone --depth 1 https://github.com/alvinunreal/oh-my-opencode-slimWhat 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.01062 |
| Opus 5 | $0.00000 | $0.00531 |
| Sonnet 5 | $0.00000 | $0.00212 |
| Haiku 4.5 | $0.00000 | $0.00106 |
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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: GitHub
Issues and PRs for this repo live as GitHub issues. Use the gh CLI for all operations. The project repo is alvinunreal/oh-my-opencode-slim.
Conventions
- Create an issue:
gh issue create --repo alvinunreal/oh-my-opencode-slim --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 --repo alvinunreal/oh-my-opencode-slim <number> --body "..." - Apply / remove labels:
gh issue edit --repo alvinunreal/oh-my-opencode-slim <number> --add-label "..."/--remove-label "..." - Close:
gh issue close --repo alvinunreal/oh-my-opencode-slim <number> --comment "..."
Infer the repo from git remote -v — gh does this automatically when run inside a clone. Write operations (create / label / comment / close) must target the upstream tracker: pass --repo alvinunreal/oh-my-opencode-slim (or set GH_REPO=alvinunreal/oh-my-opencode-slim). In a fork clone, a bare gh command would mutate your fork instead of the project tracker.
Pull requests as a triage surface
PRs as a request surface: yes. This is an open-source repo; external PRs are feature requests with attached code. They enter the triage queue for category labeling only, not the full state machine. Collaborators' in-flight PRs are excluded by the authorAssociation filter below.
Scope: category labels only. External PRs get a bug or enhancement category label based on the PR description or linked issue. They do not enter the triage state transitions and are never auto-closed during triage.
Guardrails (per council review):
- Apply only
bugorenhancementto PRs. Do not apply state labels (needs-triage,needs-info,ready-for-agent,ready-for-human,wontfix). - Never apply
good-to-codeto PRs — they are already code; the label is noise. - Never auto-close external PRs during triage. Closure stays in the review flow / maintainer decision.
- Filter on
authorAssociation, not PR content: keep CONTRIBUTOR / FIRST_TIME_CONTRIBUTOR / FIRST_TIMER / MANNEQUIN / NONE (all non-collaborator associations); drop OWNER / MEMBER / COLLABORATOR. - Keep PR triage out of issue metrics — don't mix PR counts into issue triage reporting.
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 · 45 lines · 0 tokens per session scan A 72a4395d9105
issue-tracker is an agent published in the GitHub repository alvinunreal/oh-my-opencode-slim (8,516 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,062 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
index
FlowDeck runs a 12-agent system coordinated by an orchestrator. All agent configurations live in src/agents/. Agent definitions use YAML frontmatter (description, mode, model, temperature). The orchestrator selects specialists based on context and delegates work through the OpenCode SDK delegate tool.
issue-tracker
Issues and specs (you may know a spec as a PRD) for this repo live as markdown files in .scratch/.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
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.
document-specialist
External Documentation & Reference Specialist.
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.