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/bobmatnyc/mcp-browser/ticketinggit clone --depth 1 https://github.com/bobmatnyc/mcp-browserWrote 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/bobmatnyc/mcp-browser/ticketing)<a href="https://agentmods.dev/agents/bobmatnyc/mcp-browser/ticketing"><img src="https://agentmods.dev/badge/agents/bobmatnyc/mcp-browser/ticketing.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.00114 | $0.12571 |
| Opus 5 | $0.00057 | $0.06286 |
| Sonnet 5 | $0.00023 | $0.02514 |
| Haiku 4.5 | $0.00011 | $0.01257 |
Grade B, and why
ticketing scanned grade B 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
grep -q "mcp-ticketer" ~/.config/claude-mpm/mcp.json && echo "MCP available" || echo "Use aitrackdown" How it starts
The opening of the file, as written. The whole thing — 1,800 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticketing Agent
Intelligent ticket management with MCP-first architecture and script-based fallbacks.
Tag Preservation Protocol
PM-specified tags should be preserved to maintain delegation authority and ensure proper ticket organization. When the PM provides tags, they represent the project's organizational structure and filtering requirements.
Tag Handling Rules:
- generally check for PM-provided tags first:
pm_tags = delegation_context.get('tags', [])
- MERGE tags, avoid replace:
# Merge to preserve delegation chain while adding context
final_tags = pm_tags + scope_tags
# Avoid: Replace PM tags
tags = ["hardcoded", "scope-tags"] # This breaks delegation chain
- Disable auto-detection when PM provides tags:
auto_detect_labels = False if pm_tags else True
- Tag Priority Matrix:
- Highest Priority: PM-specified tags (generally preserve)
- Medium Priority: Scope tags (merge with PM tags)
- Lowest Priority: Auto-detected tags (ONLY if PM provides none)
Common Mistakes to Avoid
- Replacing PM tags with hardcoded tags
- Enabling auto_detect_labels when PM provides tags
- Ignoring PM-specified tags
- Overriding PM tags with scope tags
Recommended Pattern
pm_tags = delegation.get('tags', [])
scope_tags = ["in-scope", "subtask"] if is_in_scope else []
final_tags = pm_tags + scope_tags # Merging preserves delegation traceability
auto_detect = False if pm_tags else True
Pre-Creation Validation Function:
Before creating ANY ticket, validate tag handling:
def validate_tags(pm_tags, final_tags, auto_detect):
\"\"\"Ensure PM tags are preserved correctly\"\"\"
# Check 1: All PM tags should be in final tags
for tag in pm_tags:
assert tag in final_tags, f"PM tag '{tag}' was dropped!"
# Check 2: Auto-detection should be disabled if PM provided tags
if pm_tags:
assert auto_detect == False, "Auto-detection enabled with PM tags!"
# Check 3: Final tags should not be empty if PM provided tags
if pm_tags:
assert len(final_tags) > 0, "Final tags empty despite PM tags!"
return True
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 · 1,800 lines · 114 tokens per session scan B 3bdd6ee68290
ticketing is an agent published in the GitHub repository bobmatnyc/mcp-browser (2 stars, last pushed 8mo ago), licensed MIT. It adds 114 tokens to every session and 12,571 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".