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/1mcp-app/agent/issue-trackergit clone --depth 1 https://github.com/1mcp-app/agentWhat 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.00323 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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 yesterday.
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 PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
Conventions
- Create an issue:
gh issue create --repo 1mcp-app/agent --title "..." --body "..." - Read an issue:
gh issue view <number> --repo 1mcp-app/agent --comments - List issues:
gh issue list --repo 1mcp-app/agent --state open --json number,title,body,labels,comments - Comment on an issue:
gh issue comment <number> --repo 1mcp-app/agent --body "..." - Apply / remove labels:
gh issue edit <number> --repo 1mcp-app/agent --add-label "..."/--remove-label "..." - Close:
gh issue close <number> --repo 1mcp-app/agent --comment "..."
When running from this clone, gh can infer the repository from git remote -v; pass --repo 1mcp-app/agent when running outside the repo or when the remote is ambiguous.
When a skill says "publish to the issue tracker"
Create a GitHub issue in 1mcp-app/agent.
When a skill says "fetch the relevant ticket"
Run gh issue view <number> --repo 1mcp-app/agent --comments.
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.
- yesterday First seen · 23 lines · 0 tokens per session scan A 88d2960c4a4a
issue-tracker is an agent published in the GitHub repository 1mcp-app/agent (494 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 323 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
code-explorer
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development. Use proactively when needing to understand how a feature works before modifying or extending it.
dotnet-framework-4.8-expert
Use this agent when working on legacy .NET Framework 4.8 enterprise applications that require maintenance, modernization, or integration with Windows-based infrastructure.
elixir-expert
Use this agent when you need to build fault-tolerant, concurrent systems leveraging OTP patterns, GenServer architectures, and Phoenix framework for real-time applications.
accessibility-tester
Use this agent when you need comprehensive accessibility testing, WCAG compliance verification, or assessment of assistive technology support.
angular-architect
Use when architecting enterprise Angular 15+ applications with complex state management, optimizing RxJS patterns, designing micro-frontend systems, or solving performance and scalability challenges in large codebases.
api-documenter
Use this agent when creating or improving API documentation, writing OpenAPI specifications, building interactive documentation portals, or generating code examples for APIs.