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/vod-studio/violet/issue-trackergit clone --depth 1 https://github.com/VOD-Studio/violetWhat 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.01162 |
| Opus 5 | $0.00000 | $0.00581 |
| Sonnet 5 | $0.00000 | $0.00232 |
| Haiku 4.5 | $0.00000 | $0.00116 |
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.
This is a copy
80% identical to issue-tracker — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: GitHub (primary) + local markdown (fallback)
Issues for this repo live on GitHub Issues as the primary tracker. When gh CLI is unavailable (offline, CI sandbox, air-gapped), fall back to local markdown under docs/issues/<prd-id>/.
Primary: GitHub Issues
Use the gh CLI for all operations.
- Create an issue:
gh issue create --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 <number> --body "..." - Apply / remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Close:
gh issue close <number> --comment "..."
Infer the repo from git remote -v — gh does this automatically when run inside a clone.
Fallback: local markdown (when gh is unavailable)
Layout follows the existing docs/issues/ convention (used by historical PRD-0001 / PRD-0002 issue breakdowns):
docs/issues/
└── <prd-id-or-slug>/ # e.g. 0002-登录态opaque-session重构/
├── 0001-<slug>.md # one file per issue, zero-padded
├── 0002-<slug>.md
└── ...
Each file uses the same body template as a GitHub issue (Parent / What to build / Acceptance criteria / Blocked by). The filename's leading number is the issue's local identifier; cross-references use 0001 style within the same PRD folder.
When to fall back: only when gh auth status fails or gh binary is missing. Otherwise always prefer GitHub — the GitHub issue number is the canonical identifier.
Historical issues under docs/issues/0005-* and docs/issues/0009-* are archived snapshots from before GitHub migration. Do not modify them; do not re-create on GitHub unless explicitly asked.
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 · 58 lines · 0 tokens per session scan A 8bb9594fe9f4
issue-tracker is an agent published in the GitHub repository VOD-Studio/violet (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,162 tokens. A static security scan graded it A with 0 findings. It is 80% identical to issue-tracker, differing in 36 lines, and is treated as a copy.
Other agents, from other repositories
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.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
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.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.