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/sponge-b0b/polaris/issue-trackergit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/sponge-b0b/polaris/issue-tracker)<a href="https://agentmods.dev/agents/sponge-b0b/polaris/issue-tracker"><img src="https://agentmods.dev/badge/agents/sponge-b0b/polaris/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.01754 |
| Opus 5 | $0.00000 | $0.00877 |
| Sonnet 5 | $0.00000 | $0.00351 |
| Haiku 4.5 | $0.00000 | $0.00175 |
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 3d 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 — 106 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.
Lifecycle authority
GitHub commands and connector operations are tracker mechanics, not permission to create or mutate workflow artifacts.
Agents must create, publish, close, reopen, or otherwise perform lifecycle-significant mutation of a workflow issue only through the skill that owns that artifact's lifecycle. A tool capability, this document, repository write access, or a request to "record" or "track" work does not by itself authorize direct issue creation or lifecycle mutation.
Before creating any issue, identify the lifecycle-owning skill and follow its publication/approval contract. If no existing skill owns the proposed artifact type, do not create the issue directly; keep the information in the appropriate repository artifact or surface the missing workflow owner.
Direct issue reads and mechanical operations are allowed only when an owning skill or explicit repository procedure authorizes them for the active lifecycle.
Conventions
The commands below describe mechanics to use when the applicable lifecycle owner authorizes the operation.
-
Create an issue: use
gh issue create --title "..." --body "..."only for simple single-line bodies. For Markdown or any multi-line body, use a literal heredoc through--body-file -so shell syntax is never expanded:gh issue create \ --title "..." \ --body-file - <<'EOF' Markdown containing `symbols`, $variables, $(commands), and other shell-sensitive text stays literal. EOFDo not use an unquoted heredoc delimiter or interpolate a multi-line body through the shell.
-
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 / remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." -
Close:
gh issue close <number> --comment "..."
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.
- 3d ago First seen · 106 lines · 0 tokens per session scan A 678997f34ef3
issue-tracker is an agent published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,754 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-31.
Other agents, from other repositories
GLOBAL
Agent "GLOBAL" from cft0808/edict, covering 全局指令 — 所有 agent 共享, ⚠️ 看板操作强制规则, 看板命令参考, 更新状态 and 流转记录.
ci-local
Run all CI checks locally and systematically fix any failures. Replicates GitHub workflow validations.
work-verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional.
debugger
Debugging specialist for errors and test failures. Use when encountering issues.
test-runner
Test automation expert. Use proactively to run tests and fix failures.
pm-lead
You are pm-lead — the great-pm orchestrator. You run the product loop. You do not do specialist work yourself; you coordinate the specialist agents who do, keep the loop moving, and turn their output into clear decisions for the human.