issue-tracker

Repository guidance stating that issues and product requirements are stored as GitHub issues. The gh CLI is GitHub's command-line tool.

In plain words
What is it for?
It is for reading and managing repository issues and product requirements through the gh CLI.
Why use it?
It gives agents the required place and tool for tracking project work.

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/calicastle/cali.so/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/CaliCastle/cali.so
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 1,013 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.01013
Opus 5 $0.00000 $0.00507
Sonnet 5 $0.00000 $0.00203
Haiku 4.5 $0.00000 $0.00101

Measured yesterday against content hash 52e9f9f1ec0f, 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 · 46 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 46 lines · 0 tokens per session scan A 52e9f9f1ec0f

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository CaliCastle/cali.so (2,024 stars, last pushed 8d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,013 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.

Related

Other agents, from other repositories

merge-conflict-resolver

Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…

module-federation/core · 264 tokens

code-refactorer

Use this agent when the user requests code refactoring, code improvement, code cleanup, or optimization of existing code. This includes requests to make code more maintainable, reduce duplication, improve performance, enhance readability, or align with best practices. The agent should be invoked proactively after the…

tutur3u/platform · 293 tokens

code-reviewer

Reviews a change against this repository's layer, tenancy, security and testing contracts. Use proactively after completing a feature or before opening a pull request.

krivoox/agent-stack-template · 33 tokens

devops-engineer

Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.

krivoox/agent-stack-template · 47 tokens

visual-debug-iterator

Iterate Phase 7 visual-fix cycles in a separate context with vision-free hard rule (no PNG/JPG/WebP reads). Invoked after section-compare.sh or tree-diff.sh reports FAIL. Reads gate text outputs (auto-diagnose, tree-diff-status, computed-diff), applies ONE scoped fix per iteration, re-runs gate, max 5 iterations.…

voidmatcha/ui-clone-skills · 130 tokens

generation-planner

Enrich generation-plan.json from schemaVersion 1 to 2 with semantic token names, ds-components groupings, per-component library wires, signature effects, and sticky/pin mechanisms. Invoked at Phase 6 7-pre after scripts/extract/generation-plan.sh has produced the deterministic base. Reads the operational contract from…

voidmatcha/ui-clone-skills · 89 tokens