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/rob-balfre/dryui/issue-trackergit clone --depth 1 https://github.com/rob-balfre/dryuiWhat 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.00267 |
| Opus 5 | $0.00000 | $0.00133 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00027 |
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 repo live as GitHub issues in rob-balfre/dryui. Use gh-axi for GitHub operations in this repository.
Conventions
- Create an issue:
gh-axi issue create --title "..." --body "...". Use a heredoc for multi-line bodies. - Read an issue:
gh-axi issue view <number> --comments, including labels and relevant comments. - List issues:
gh-axi issue list --state openwith appropriate label and state filters. - Comment on an issue:
gh-axi issue comment <number> --body "..." - Apply / remove labels:
gh-axi issue edit <number> --add-label "..."/--remove-label "..." - Close:
gh-axi issue close <number> --comment "..."
Infer the repo from git remote -v. The canonical remote is https://github.com/rob-balfre/dryui.git.
When a skill says "publish to the issue tracker"
Create a GitHub issue.
When a skill says "fetch the relevant ticket"
Run gh-axi issue view <number> --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.
- 2d ago First seen · 23 lines · 0 tokens per session scan A 28e0e80f2936
issue-tracker is an agent published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 267 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
svelte-expert
Svelte framework expert agent for component development and SvelteKit applications.
investigate-error
Investigates React compiler errors to determine the root cause and identify potential mitigation(s). Use this agent when the user asks to 'investigate a bug', 'debug why this fixture errors', 'understand why the compiler is failing', 'find the root cause of a compiler issue', or when they provide a snippet of code and…
analyze-pass-impact
Analyzes how a specific topic affects a group of compiler passes. Used by the /plan-update skill to parallelize research across all compiler phases. Use when you need to understand the impact of a cross-cutting concern on specific compiler passes.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
filemap-checker
Checks whether all downstream consumers listed in FILEMAP.md have been updated after a change. Use proactively after modifying files.
test-writer
Writes tests for backend and frontend code. Use for test-only tasks: backfilling coverage, regression tests for a reported bug, or expanding an existing suite. Engineer agents write tests alongside their own features - do not double-delegate those.