issue-tracker

issue-tracker is an agent for coding agents from Contrast-Security-OSS/mcp-contrast. It costs 0 tokens per session (1,044 once invoked), scanned A, original, Apache-2.0.

A reference for managing work items in a project that uses Beads as its local issue store and Jira as its external tracker. Beads is a repository-local work database, while Jira is a shared issue-management system.

In plain words
What is it for?
Use it when creating or updating Beads issues, linking work to Jira, choosing the right Git branch, or deciding whether GitHub Issues applies.
Why use it?
It clarifies which system to use for each issue and helps keep local work, Jira tickets, branches, and pull requests aligned.

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/contrast-security-oss/mcp-contrast/issue-tracker
Clone the repo
git clone --depth 1 https://github.com/Contrast-Security-OSS/mcp-contrast

Wrote 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.

agentmods badge for issue-tracker

README.md
[![agentmods](https://agentmods.dev/badge/agents/contrast-security-oss/mcp-contrast/issue-tracker.svg)](https://agentmods.dev/agents/contrast-security-oss/mcp-contrast/issue-tracker)
Your own site
<a href="https://agentmods.dev/agents/contrast-security-oss/mcp-contrast/issue-tracker"><img src="https://agentmods.dev/badge/agents/contrast-security-oss/mcp-contrast/issue-tracker.svg" alt="Measured on agentmods" height="20"></a>
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,044 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.01044
Opus 5 $0.00000 $0.00522
Sonnet 5 $0.00000 $0.00209
Haiku 4.5 $0.00000 $0.00104

Measured 4d ago against content hash b004e851aa6e, 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 4d 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 · 44 lines

How it starts

The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issue tracker (beads + Jira)

Issues for this repo run on a dual model. Beads (br) is the working issue store and Jira (the AIML project, component Contrast MCP Server) is the external reference. The gh CLI is used for pull requests, not for issues. GitHub Issues is not the tracker for this repo.

When a skill says "the issue tracker", it means beads first, with Jira as the linked external ticket for anything that needs one. Most code changes need a Jira ticket and a feature branch (AIML-<id>-<desc>) before merging.

The bead-workflow skill governs every bead mutation and the jira-workflow skill governs ticket creation, bead-to-Jira parity, and status transitions. This doc is the quick reference.

Beads is the primary store

The database lives in this repo's .beads/, which is gitignored and local-only. This is a public repository, never commit anything under .beads/.

  • Create: br create "Title" --description "..." --type task --priority 2 --labels "repo:mcp-contrast". For multi-line content use a quoted heredoc through $() to keep markdown, backticks, and $(vars) literal. For the design field use scripts/br-set-design <bead-id> <file>.
  • Start work: br update <bead-id> --claim sets assignee and status atomically. Falls back to --status in_progress --assignee <you> when a stacked-branch blocks edge makes the bead "blocked" (see the bead-workflow skill).
  • Find work: br ready lists unblocked open beads. br list and br show <bead-id> for detail. br search "keyword" for full text.
  • Comment: br comments add <bead-id> --message "..." for one line, or br comments add <bead-id> -f /tmp/comment.txt for multi-line. Note br comment (singular) does not exist.
  • Label: br label add <bead-id> -l <label> / br label remove <bead-id> -l <label>. See triage-labels.md for the vocabulary.
  • Dependencies: br dep add <dependent> <prerequisite> for a blocks edge, br dep add <child> <parent> --type parent-child for hierarchy.
  • Close: br close <bead-id> --reason "why it's done". The --reason/-r flag is required. Ask the user before closing a bead, and close child beads before their parent.
  • Sync: br sync --flush-only exports the DB to the local JSONL after mutations and before ending a session.

Read the full file on GitHub · 44 lines

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. 4d ago First seen · 44 lines · 0 tokens per session scan A b004e851aa6e

Subscribe to this mod's changes

issue-tracker is an agent published in the GitHub repository Contrast-Security-OSS/mcp-contrast (23 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,044 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.