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/drsh4dow/bevy-agent-feedback-plugin/issue-trackergit clone --depth 1 https://github.com/drsh4dow/bevy-agent-feedback-pluginWhat 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.01013 |
| Opus 5 | $0.00000 | $0.00507 |
| Sonnet 5 | $0.00000 | $0.00203 |
| Haiku 4.5 | $0.00000 | $0.00101 |
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 46 lines · 0 tokens per session scan A 52e9f9f1ec0f
issue-tracker is an agent published in the GitHub repository drsh4dow/bevy-agent-feedback-plugin (2 stars, last pushed 1mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,013 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
project-owner
Business-focused product owner agent – clarify business goals, manage Jira work, align stakeholders, coordinate scope, acceptance criteria, assumptions, risks.
worker-executor
Execute pre-approved mutations — Jira transitions, Linear updates, API calls, build commands.
plan-orchestrator
THE BRAIN of Toh Framework - analyzes requests/PRDs, writes the plan artifact .toh/plan.md, holds one approval gate, then runs the autonomous TOH LOOP. Delegate when: complex multi-step tasks, project planning, PRD analysis, feature breakdown, or when a plan.md structure needs drafting/refreshing. Self-sufficient…
product_manager
Product management specialist for requirements gathering, PRDs, user stories, feature prioritization, and competitive analysis. Use when the task requires defining product requirements, writing user stories with acceptance criteria, prioritizing features, or conducting competitive research. For example: writing a PRD…
ref-tracker
Classify reference projects, maintain references/INDEX.md, and emit BA design reference triplet rows.
hatch3r-dependency-drafter
Dependency-analysis specialist who drafts version-bump and dependency-change proposals — assesses upgrade impact, security advisories, and breaking changes, then hands a reviewable proposal to a separate reviewer/applier. Drafts only; never installs, edits a manifest, or applies an upgrade. Use when planning a…