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/debpalash/voicestudio/issue-trackergit clone --depth 1 https://github.com/debpalash/VoiceStudioWrote 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/debpalash/voicestudio/issue-tracker)<a href="https://agentmods.dev/agents/debpalash/voicestudio/issue-tracker"><img src="https://agentmods.dev/badge/agents/debpalash/voicestudio/issue-tracker.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.00000 | $0.01292 |
| Opus 5 | $0.00000 | $0.00646 |
| Sonnet 5 | $0.00000 | $0.00258 |
| Haiku 4.5 | $0.00000 | $0.00129 |
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 4d 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
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 66 lines · 0 tokens per session scan A d5f2b8e3e2a2
issue-tracker is an agent published in the GitHub repository debpalash/VoiceStudio (13,789 stars, last pushed yesterday), licensed AGPL-3.0. It costs nothing until one of its globs matches a file; then it loads 1,292 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
perf-test-sync
Use this agent when the user needs to synchronize performance test cases between development (dev) and QA directories, compare test configurations, update test lists, or analyze gaps between dev and QA perf test coverage. This includes syncing aggregated and disaggregated performance test cases, updating QA test lists…
ad-onboard-reviewer
Independent reviewer for AutoDeploy model onboarding. Validates created model and test files against all onboarding requirements. Use after completing model onboarding work.
ad-run-agent
Run AutoDeploy build and run command for a given model.
kernel-cute-specialist
Expert in writing optimized GPU kernels using CuTe DSL for NVIDIA GPUs (Ampere through Blackwell). This is the CuTe DSL specialist -- NOT Triton. CuTe DSL uses cute.jit/cute.kernel decorators and cutlass.cute imports; Triton uses triton.jit and tl. primitives -- they are completely different frameworks. Delegate to…
ad-debug-agent
Debug the AutoDeploy model onboarding process.
exec-compile-specialist
Compiles TensorRT-LLM from source. Handles two scenarios: (1) compiling directly on a compute node inside a dev Docker container, and (2) submitting a SLURM batch job from a login node with enroot container support. Detects the environment automatically, gathers required parameters, runs the build, monitors progress…