issue-tracker

A set of rules for managing this repository's work through GitHub issues, which are pages used to track tasks, bugs, and product requirements. It also defines how to read, label, comment on, create, and close those issues with the GitHub command-line tool.

In plain words
What is it for?
Use it to publish work as GitHub issues, fetch issue details and comments, manage labels, record blockers, and check whether a task is ready.
Why use it?
It keeps project requests and their dependencies in one place and makes the repository's issue workflow consistent.

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/chenweil/skillcaddy/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/chenweil/skillcaddy
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 249 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.00249
Opus 5 $0.00000 $0.00125
Sonnet 5 $0.00000 $0.00050
Haiku 4.5 $0.00000 $0.00025

Measured 2d ago against content hash bead8fcfcf0c, 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 2d 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.

docs/agents/issue-tracker.md · 34 lines

What it actually says

Issue tracker: GitHub

Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.

Conventions

  • Create issues with gh issue create.
  • Read issues and comments with gh issue view <number> --comments.
  • List issues with gh issue list, including labels and comments when required.
  • Comment with gh issue comment.
  • Apply or remove labels with gh issue edit.
  • Close issues with gh issue close.
  • Infer the repository from the current Git remote.

Pull requests as a triage surface

PRs as a request surface: no.

GitHub shares one number space across issues and pull requests. Resolve ambiguous references before operating on them.

Skill operations

  • “Publish to the issue tracker” means creating a GitHub issue.
  • “Fetch the relevant ticket” means reading the issue body, labels, and comments.
  • Apply the configured ready-for-agent label to agent-ready specs and tickets.

Blocking relationships

Use GitHub native issue dependencies where available. Otherwise, record:

Blocked by: #<issue>, #<issue>

A ticket is ready only when every blocking issue is closed.

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. 2d ago First seen · 34 lines · 0 tokens per session scan A bead8fcfcf0c

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository chenweil/skillcaddy (24 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 249 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

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens