issue-tracker

A set of instructions for managing this repository’s work through GitHub Issues, GitHub’s system for tracking tasks, bugs, and feature plans.

In plain words
What is it for?
Creating and reading issues, checking comments and labels, and closing completed tickets with the GitHub CLI.
Why use it?
It gives the agent consistent commands for creating, finding, updating, commenting on, and closing repository issues.

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/tiangzlab/omicsclaw/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/TianGzlab/OmicsClaw
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 202 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.00202
Opus 5 $0.00000 $0.00101
Sonnet 5 $0.00000 $0.00040
Haiku 4.5 $0.00000 $0.00020

Measured yesterday against content hash 7ff781de3908, 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 · 22 lines

What it actually says

Issue tracker: GitHub

Issues and PRDs for this repository live in GitHub Issues for zhou-1314/OmicsClaw. Use the gh CLI for issue operations.

Conventions

  • Create: gh issue create --title "..." --body "...".
  • Read: gh issue view <number> --comments.
  • List: use gh issue list with explicit state, label, and JSON filters.
  • Comment: gh issue comment <number> --body "...".
  • Apply or remove labels with gh issue edit.
  • Close with gh issue close <number> --comment "...".

Infer the repository from the current clone unless a command needs an explicit --repo zhou-1314/OmicsClaw argument.

Skill vocabulary

  • "Publish to the issue tracker" means create a GitHub issue.
  • "Fetch the relevant ticket" means read the issue body, labels, and comments.
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 · 22 lines · 0 tokens per session scan A 7ff781de3908

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository TianGzlab/OmicsClaw (158 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 202 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.