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/dvnghiem/flowdeck/issue-trackergit clone --depth 1 https://github.com/DVNghiem/FlowDeckWhat 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.00474 |
| Opus 5 | $0.00000 | $0.00237 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
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.
Copies of this mod
8 near-identical copies found in the catalogue:
- issue-tracker — 100% identical, 0 lines differ
- issue-tracker — 98% identical, 2 lines differ
- issue-tracker — 98% identical, 2 lines differ
- issue-tracker — 98% identical, 6 lines differ
- issue-tracker — 98% identical, 2 lines differ
- issue-tracker — 98% identical, 6 lines differ
- issue-tracker — 94% identical, 2 lines differ
- issue-tracker — 92% identical, 2 lines differ
What it actually says
Issue tracker: Local Markdown
Issues and specs (you may know a spec as a PRD) 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, numbered from01— never a single combined tickets file - Triage state is recorded as a
Status:line near the top of each issue file (seetriage-labels.mdfor the role strings) - 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.
Wayfinding operations
Used by /wayfinder. The map is a file with one child file per ticket.
- Map:
.scratch/<effort>/map.md— the Notes / Decisions-so-far / Fog body. - Child ticket:
.scratch/<effort>/issues/NN-<slug>.md, numbered from01, with the question in the body. AType:line records the ticket type (research/prototype/grilling/task); aStatus:line recordsclaimed/resolved. - Blocking: a
Blocked by: NN, NNline near the top. A ticket is unblocked when every file it lists isresolved. - Frontier: scan
.scratch/<effort>/issues/for files that are open, unblocked, and unclaimed; first by number wins. - Claim: set
Status: claimedand save before any work. - Resolve: append the answer under an
## Answerheading, setStatus: resolved, then append a context pointer (gist + link) to the map's Decisions-so-far 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.
- yesterday First seen · 31 lines · 0 tokens per session scan A ed6add9fe3cd
issue-tracker is an agent published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 474 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").
build-agent-empty-input-diagnosis
Status: Resolved for interview injections. Date: 2026-08-10 Related PR: #818 (fix/preset-tui-slash-command) — same root class as the original /preset fix. Suspected sibling bug reported by user: During superpowers / brainstorm skill conversations, when the orchestrator asks for confirmation or work is interrupted…
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
issue-tracker
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.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
sprint-prioritizer
Expert in backlog grooming, story sizing, sprint planning, and agile methodology.