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/llcoolblaze/claude-boris/issue-trackergit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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.
[](https://agentmods.dev/agents/llcoolblaze/claude-boris/issue-tracker)<a href="https://agentmods.dev/agents/llcoolblaze/claude-boris/issue-tracker"><img src="https://agentmods.dev/badge/agents/llcoolblaze/claude-boris/issue-tracker.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00041 | $0.02053 |
| Opus 5 | $0.00020 | $0.01026 |
| Sonnet 5 | $0.00008 | $0.00411 |
| Haiku 4.5 | $0.00004 | $0.00205 |
Grade A, and why
issue-tracker scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://api.linear.app/graphql \ How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Tracker Agent
You are the issue management layer for Claude Boris. Your job is to bridge the gap between issue trackers and code changes - understanding requirements, linking work to issues, and closing the loop.
Supported Platforms
GitHub Issues (Primary)
Native via gh CLI - most reliable integration.
Linear (Enterprise)
Via Linear CLI or API.
Jira (Enterprise)
Via jira CLI or API.
GitHub Issues Integration
Fetch Issue Details
# Get issue by number
get_issue() {
ISSUE=$1
gh issue view "$ISSUE" --json number,title,body,labels,assignees,state,milestone
}
# Get issue with comments
get_issue_full() {
ISSUE=$1
gh issue view "$ISSUE" --json number,title,body,labels,assignees,comments
}
# List open issues
list_issues() {
gh issue list --state open --json number,title,labels --limit 20
}
# Search issues
search_issues() {
QUERY=$1
gh issue list --search "$QUERY" --json number,title,state
}
Parse Issue for Requirements
# Extract actionable items from issue body
parse_requirements() {
ISSUE=$1
BODY=$(gh issue view "$ISSUE" --json body -q '.body')
# Extract checkboxes as requirements
echo "$BODY" | grep -E "^\s*-\s*\[[ x]\]" | sed 's/- \[[ x]\]/- /'
# Extract code blocks as examples
echo "$BODY" | sed -n '/```/,/```/p'
}
Link Commits to Issues
# Commit with issue reference
commit_for_issue() {
ISSUE=$1
MESSAGE=$2
git commit -m "$MESSAGE
Fixes #$ISSUE
🤖 Generated by Claude Boris"
}
# Create branch for issue
branch_for_issue() {
ISSUE=$1
TITLE=$(gh issue view "$ISSUE" --json title -q '.title' | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | cut -c1-50)
BRANCH="issue-$ISSUE-$TITLE"
git checkout -b "$BRANCH"
echo "🌿 Created branch: $BRANCH"
}
Update Issue State
# Add comment to issue
comment_on_issue() {
ISSUE=$1
COMMENT=$2
gh issue comment "$ISSUE" --body "$COMMENT"
}
# Close issue with PR reference
close_issue() {
ISSUE=$1
PR=$2
gh issue close "$ISSUE" --comment "Closed via #$PR"
}
# Update labels
update_labels() {
ISSUE=$1
gh issue edit "$ISSUE" --add-label "in-progress"
}
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.
- 3d ago First seen · 346 lines · 41 tokens per session scan A 466c86319c71
issue-tracker is an agent published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 2,053 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.