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/pumblus/okf-harness/issue-trackergit clone --depth 1 https://github.com/pumblus/okf-harnessWrote 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/pumblus/okf-harness/issue-tracker)<a href="https://agentmods.dev/agents/pumblus/okf-harness/issue-tracker"><img src="https://agentmods.dev/badge/agents/pumblus/okf-harness/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 | $0.00000 | $0.00777 |
| Opus 5 | $0.00000 | $0.00388 |
| Sonnet 5 | $0.00000 | $0.00155 |
| Haiku 4.5 | $0.00000 | $0.00078 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: GitHub
Issues and PRDs live as GitHub issues; use the gh CLI for all operations.
Conventions
- Create:
gh issue create --title "..." --body "..."(heredoc for multi-line bodies). - Read:
gh issue view <number> --comments, fetching labels too and filtering comments withjq. - List:
gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'with--label/--statefilters as needed. - Comment:
gh issue comment <number> --body "..." - Labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Close:
gh issue close <number> --comment "..."
PRs as a triage surface
Flag: no — external PRs are not feature requests; /triage reads this flag. Set to yes to route PRs through the same labels and states:
- Read:
gh pr view <number> --comments;gh pr diff <number>for the diff. - List external PRs:
gh pr list --state open --json number,title,body,labels,author,authorAssociation,comments, keeping onlyCONTRIBUTOR,FIRST_TIME_CONTRIBUTOR, orNONEauthors. - Comment / label / close:
gh pr comment,gh pr edit --add-label/--remove-label,gh pr close.
Issues and PRs share one number space; resolve a bare #42 with gh pr view 42, falling back to gh issue view 42.
Skill verbs
- "Publish to the issue tracker" → create a GitHub issue.
- "Fetch the relevant ticket" →
gh issue view <number> --comments.
Wayfinding (/wayfinder)
The map is one issue; its tickets are child issues. This repo has sub-issues and native issue dependencies enabled and the wayfinder:* labels exist — use the native mechanisms; no task-list or Blocked by: fallbacks.
- Map: issue labelled
wayfinder:mapholding the Destination / Notes / Decisions-so-far / Fog body;gh issue create --label wayfinder:map. - Child ticket: link to the map as a sub-issue via
gh api repos/<owner>/<repo>/issues/<map>/sub_issues; labelwayfinder:<type>(research/prototype/grilling/task); assign to the driving dev once claimed. - Blocking:
gh api --method POST repos/<owner>/<repo>/issues/<child>/dependencies/blocked_by -F issue_id=<blocker-db-id>— the blocker's numeric database id (gh api repos/<owner>/<repo>/issues/<n> --jq .id), not the#numberornode_id. Open blockers appear inissue_dependencies_summary.blocked_by; a ticket is unblocked when all blockers are closed. - Frontier: the map's open sub-issues minus any with open blockers or assignees, in map order.
- Claim:
gh issue edit <n> --add-assignee @me— the session's first write. - Resolve: comment the answer, close the issue, then append a context pointer (gist + link) 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.
- 4d ago First seen · 39 lines · 0 tokens per session scan A 4bd54c5e8312
issue-tracker is an agent published in the GitHub repository pumblus/okf-harness (34 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 777 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
eval-skew-reviewer
Reviews diffs that add or change a write-time enrichment feature / retrieval channel for training-serving skew — verifies the feature is wired into the ONE canonical ingest path AND the eval seed AND the seed liveness contract, so it can't ship "merged-but-inert". Use after changes touching ingest enrichment, a new…
doc-drift-auditor
Read-only audit for fuzzy drift the CI teeth (driftguard.rs) cannot catch — eval numbers stale vs the current env-hash, design-doc/decision rot, memory->repo dangling pointers, and stale worktrees. Run locally on a schedule. Produces a findings report only; never edits.
discoverer
You are the Discoverer. Your job is to find and inventory the source material — files, data, configs, code — that will feed downstream agents (Packager, Migrator, etc.).
product-manager
Use this agent for product development coordination, tracking tasks (GitHub Issues or local markdown), sprint planning, progress reporting, and development ceremony management. This PM does NOT use Jira.
tester
You are the Tester. You are the other half of the 2-agent rule from CLAUDE.md — you independently verify that the Worker (Packager / Migrator / Coder) did the job correctly.
personal-assistant
Capture, triage, and maintain personal tasks, schedules, and personal project progress through a Kanban-first workflow.