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/sbroenne/mcp-server-excel/issue-trackergit clone --depth 1 https://github.com/sbroenne/mcp-server-excelWhat 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.00000 | $0.00357 |
| Opus 5 | $0.00000 | $0.00179 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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.
What it actually says
Issue tracker: GitHub
Issues and specifications for this repository live in GitHub Issues. Use the gh command-line tool for all operations.
Conventions
- Infer the repository from the current Git remote.
- Pull requests are not treated as incoming work requests.
- A bare
#42may identify an issue or pull request; check the pull request first, then the issue. - When a skill says "publish to the issue tracker," create a GitHub issue.
- When a skill says "fetch the relevant ticket," read that GitHub issue and its comments.
Choose the matching issue template
Read and preserve the headings from the closest template:
- General defect:
.github/ISSUE_TEMPLATE/bug_report.md - MCP Server defect:
.github/ISSUE_TEMPLATE/mcp_server_issue.md - New or changed behavior:
.github/ISSUE_TEMPLATE/feature_request.md
Fill every section that applies. Use N/A when a required section does not apply, and never include private workbook data, credentials, or customer information.
breaking-changes-issue.md is a historical implementation plan, not a template for new issues.
GitHub operations
- Create:
gh issue create --title "..." --body-file <path> - Read:
gh issue view <number> --comments --json number,title,body,labels,comments,state - List:
gh issue list --state open --json number,title,body,labels - Comment:
gh issue comment <number> --body "..." - Add or remove labels:
gh issue edit <number> --add-label "..."or--remove-label "..." - Close:
gh issue close <number> --comment "..."
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.
- 2d ago First seen · 33 lines · 0 tokens per session scan A 54c97566138c
issue-tracker is an agent published in the GitHub repository sbroenne/mcp-server-excel (645 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 357 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.
Other agents, from other repositories
Atlassian Requirements to Jira
Transform requirements documents into structured Jira epics and user stories with intelligent duplicate detection, change management, and user-approved creation workflow.
TaskTracker
Reads, parses, and returns the list of tasks from tasks.md in a structured format.
agent-workflows
How Projektor fits the agentic dev-tools stack, and the end-to-end multi-agent loop: lifecycle, coordination, and project management.
sddp-wbs-generator
Generates, validates, and writes tasks.md based on project design artifacts.
github-issue-tracker
Use this agent when you need to create, manage, or track GitHub issues during development workflows. Creates properly formatted issues with context, labels, and assignees. Read-only agent for production safety.
business-metrics-analyzer
Analyzes pipeline logs to generate business-facing metrics including velocity, cost per feature, quality trends, and scope creep indicators.