issue-tracker

Repository guidance for managing issues and product requirements through GitHub. It identifies the project repository and documents commands for viewing, creating, labeling, commenting on, and closing issues.

In plain words
What is it for?
Use it when finding related issues, creating requirements, updating issue labels, adding comments, or closing completed work.
Why use it?
It keeps project decisions and requirements in the repository’s established issue-tracking system instead of separate tools.

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/cliftonc/drizzle-cube/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/cliftonc/drizzle-cube
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 336 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 77% copy Near-identical to another mod 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.00336
Opus 5 $0.00000 $0.00168
Sonnet 5 $0.00000 $0.00067
Haiku 4.5 $0.00000 $0.00034

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

Origin

This is a copy

77% identical to issue-tracker — 12 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.

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

What it actually says

Issue tracker: GitHub

Issues and PRDs for this repo live as GitHub issues in cliftonc/drizzle-cube. Use the gh CLI for all operations.

This clone has a single origin pointing at cliftonc/drizzle-cube, so gh infers the repo automatically. Passing -R cliftonc/drizzle-cube explicitly is still the safest habit if another remote is ever added.

Conventions

  • 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 by jq and 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 --label and --state filters.
  • 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 "..."

When a skill says "publish to the issue tracker"

Create a GitHub issue in cliftonc/drizzle-cube.

When a skill says "fetch the relevant ticket"

Run gh issue view <number> --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. 2d ago First seen · 23 lines · 0 tokens per session scan A 41a5931f18b0

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository cliftonc/drizzle-cube (58 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 336 tokens. A static security scan graded it A with 0 findings. It is 77% identical to issue-tracker, differing in 12 lines, and is treated as a copy.

Related

Other agents, from other repositories

pbip-validator

Validate Power BI Project (PBIP) file structure, TMDL syntax, and PBIR JSON schemas. Dispatch when the user asks to "validate my PBIP project", "check if the rename cascade is complete", "is this visual.json valid", or "my PBIP won't open".

data-goblin/power-bi-agentic-development · 63 tokens

semantic-model-auditor

Audit semantic models for quality, performance, and best practice violations. Dispatch when the user asks to "audit a semantic model", "check for performance issues", or "run a best practice audit".

data-goblin/power-bi-agentic-development · 45 tokens

query-listener

Capture DAX queries generated by Power BI Desktop visuals in real time. Dispatch when the user wants to "capture visual queries", "see what DAX is being sent", "intercept PBI queries", "listen for visual queries", "capture Performance Analyzer queries", or "see what queries my visuals generate".

data-goblin/power-bi-agentic-development · 66 tokens

bpa-expression-helper

Debug, improve, or explain BPA rule expressions. Invoke when users ask to "fix my BPA expression", "why isn't my rule working", "help with Dynamic LINQ", or need assistance writing complex BPA rule expressions.

data-goblin/power-bi-agentic-development · 49 tokens

deneb-reviewer

Review a Deneb visual spec before presenting it to the user. Validates Vega/Vega-Lite syntax, Deneb-specific conventions, and provides design feedback.

data-goblin/power-bi-agentic-development · 37 tokens

python-reviewer

Review a Python visual script before presenting it to the user. Validates matplotlib/seaborn code, Power BI conventions, and provides design feedback.

data-goblin/power-bi-agentic-development · 33 tokens