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/michaelwilhelmsen/humla/issue-trackergit clone --depth 1 https://github.com/michaelwilhelmsen/humlaWrote 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/michaelwilhelmsen/humla/issue-tracker)<a href="https://agentmods.dev/agents/michaelwilhelmsen/humla/issue-tracker"><img src="https://agentmods.dev/badge/agents/michaelwilhelmsen/humla/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.01187 |
| Opus 5 | $0.00000 | $0.00593 |
| Sonnet 5 | $0.00000 | $0.00237 |
| Haiku 4.5 | $0.00000 | $0.00119 |
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.
This is a copy
84% identical to issue-tracker — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: GitHub
Issues and PRDs for this repo live as GitHub issues in michaelwilhelmsen/humla. Use the gh CLI for all operations.
Conventions
- Create an issue:
gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies. - Read an issue:
gh issue view <number> --comments, filtering comments byjqand also fetching labels. - List issues:
gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'with appropriate--labeland--statefilters. - Comment on an issue:
gh issue comment <number> --body "..." - Apply / remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Close:
gh issue close <number> --comment "..."
Infer the repo from git remote -v — gh does this automatically when run inside a clone.
Pull requests as a triage surface
PRs as a request surface: no. (Set to yes if this repo treats external PRs as feature requests; /triage reads this flag.)
When set to yes, PRs run through the same labels and states as issues, using the gh pr equivalents:
- Read a PR:
gh pr view <number> --commentsandgh pr diff <number>for the diff. - List external PRs for triage:
gh pr list --state open --json number,title,body,labels,author,authorAssociation,commentsthen keep onlyauthorAssociationofCONTRIBUTOR,FIRST_TIME_CONTRIBUTOR, orNONE(dropOWNER/MEMBER/COLLABORATOR). - Comment / label / close:
gh pr comment,gh pr edit --add-label/--remove-label,gh pr close.
GitHub shares one number space across issues and PRs, so a bare #42 may be either — resolve with gh pr view 42 and fall back to gh issue view 42.
When a skill says "publish to the issue tracker"
Create a GitHub issue.
When a skill says "fetch the relevant ticket"
Run gh issue view <number> --comments.
Wayfinding operations
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 · 54 lines · 0 tokens per session scan A 0bda05ec99f3
issue-tracker is an agent published in the GitHub repository michaelwilhelmsen/humla (270 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,187 tokens. A static security scan graded it A with 0 findings. It is 84% identical to issue-tracker, differing in 18 lines, and is treated as a copy.
Other agents, from other repositories
matrix
This page renders the Tier-1 agent × model-family integration matrix truthfully from the authoritative test suite in tests/integrations/ — the matrix cells (testagentsmatrix.py), the family aliases and strict-xfail rules (conftest.py), and the pilot run recorded in tests/integrations/README.md.
claude-code
Point Anthropic's Claude Code at a local rapid-mlx server. Claude Code speaks the Anthropic Messages API (POST /v1/messages); rapid-mlx implements that route natively, so you can drive Claude Code with any local model.
opencode
Point OpenCode at a local rapid-mlx server. OpenCode is a Claude-Code-like terminal coding agent that speaks the OpenAI-compatible chat completions API (POST /v1/chat/completions) via the @ai-sdk/openai-compatible provider.
openhands
Point OpenHands (formerly OpenDevin) at a local rapid-mlx server. OpenHands drives its CodeActAgent inside a Docker sandbox and reaches the model over the OpenAI-compatible chat completions API (POST /v1/chat/completions) via LiteLLM.
qwen-code
Point Qwen Code at a local rapid-mlx server. Qwen Code is Alibaba's gemini-cli fork tuned for Qwen tool-calling; it speaks the OpenAI-compatible chat completions API (POST /v1/chat/completions) via an OpenAI entry in modelProviders that maps 1:1 onto rapid-mlx's default endpoint.
deepseek-harness
Run the official DeepSeek Harness against a local Rapid-MLX server. Rapid uses Harness's generic openai-completions provider; it does not impersonate the DeepSeek cloud API.