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/barrosohub/frontend-stack-blueprint/issue-trackergit clone --depth 1 https://github.com/barrosohub/frontend-stack-blueprintWhat 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.00221 |
| Opus 5 | $0.00000 | $0.00111 |
| Sonnet 5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
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 PRDs for this repository live in GitHub Issues.
Conventions
- Prefer the connected GitHub integration for issue and pull-request operations.
- When the GitHub CLI is available, infer the repository from
git remote -v. - Create one issue per independently deliverable change.
- Read the issue body, labels, and comments before implementation.
- Link pull requests to their originating issue when one exists.
- Use GitHub-native sub-issues and dependencies for blocked work when available.
Pull requests as a triage surface
PRs as a request surface: no.
External pull requests are reviewed as proposed changes, not treated as feature requests by default.
Skill operations
- When a skill says publish to the issue tracker, create a GitHub issue.
- When a skill says fetch the relevant ticket, read the corresponding issue body, labels, and comments.
- Resolve a bare
#42as either an issue or pull request before acting because GitHub shares one number space between them.
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 · 28 lines · 0 tokens per session scan A dcdc8ee6466a
issue-tracker is an agent published in the GitHub repository barrosohub/frontend-stack-blueprint (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 221 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-31.
Other agents, from other repositories
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
waves-controller
You are a wave execution orchestrator. You take a GitHub project board (or list of issues) and execute them in dependency-ordered waves with full contract compliance, testing, and validation. You coordinate all other Specflow agents through an 8-phase workflow.
board-auditor
You are a board compliance auditor. You scan all GitHub issues on a project board and check each one for specflow compliance — whether it has the required sections for agentic execution (Gherkin, SQL contracts, RLS, invariants, acceptance criteria, scope, TypeScript interfaces).
specflow-uplifter
You are a specflow remediation specialist. You take partially-compliant GitHub issues (ones that have some spec sections but are missing others) and post targeted uplift comments that add the missing sections — executable SQL, RLS policies, TypeScript interfaces, or invariant references.
sprint-executor
You are a sprint execution coordinator. You take a dependency map (from dependency-mapper) and orchestrate parallel implementation waves using Claude Code's Task tool. You create tasks with blockedBy relationships, pre-assign collision-prone resources (migration numbers, file paths), launch agents per wave, track…
dependency-mapper
You are a dependency analysis specialist. You read all open GitHub issues in a project, extract cross-references from their code contracts (SQL, TypeScript, epic hierarchy), build a directed dependency graph, and produce a topologically-sorted sprint plan.