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/miaodx/roboclaws/issue-trackergit clone --depth 1 https://github.com/MiaoDX/roboclawsWhat 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.00223 |
| Opus 5 | $0.00000 | $0.00112 |
| Sonnet 5 | $0.00000 | $0.00045 |
| 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 repo live as GitHub issues. Use the gh CLI for all
operations.
Repository: MiaoDX/roboclaws
Conventions
- Create an issue:
gh issue create --title "..." --body "..." - Read an issue:
gh issue view <number> --comments - List issues:
gh issue list --state open --json number,title,body,labels,comments - Comment on an issue:
gh issue comment <number> --body "..." - Apply or remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Close an issue:
gh issue close <number> --comment "..."
Infer the repo from git remote -v; gh does this automatically inside this
clone.
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.
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 · 29 lines · 0 tokens per session scan A f072e5002c03
issue-tracker is an agent published in the GitHub repository MiaoDX/roboclaws (6 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 223 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
GLOBAL
Agent "GLOBAL" from cft0808/edict, covering 全局指令 — 所有 agent 共享, ⚠️ 看板操作强制规则, 看板命令参考, 更新状态 and 流转记录.
discussion-spec
작업일지가 무엇을 했나(회고), 플래너가 무엇을, 어디까지(결정 후 계획)라면, 문제 해결 문서(.oculpm/discussion/ /discussion.md)는 그 앞 단계 — "이게 문제인가? 어떤 안들이 있나?" 를 결정 전에 정리하는 회의록입니다.
tracker-syncer
Specialist for tracker synchronization. Invoked by /push-to-tracker and /sync-status. Dispatches per .forge/settings.yaml tracker.type (linear|github|notion).
product-decomposer
Specialist for breaking specs into phases.yaml. Invoked by /decompose.
phase-gatekeeper
Ceremonial specialist for advancing phases. Invoked by /phase-gate.
project-manager
Use this agent when you need comprehensive project oversight and coordination. Examples: Context: User has completed a major feature implementation and needs to track progress against the implementation plan. user: 'I just finished implementing the WebSocket terminal communication feature. Can you check our progress…