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/landing-ai/ade-cli/issue-trackergit clone --depth 1 https://github.com/landing-ai/ade-cliWhat 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 yesterday.
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.
Copies of this mod
8 near-identical copies found in the catalogue:
- issue-tracker — 100% identical, 0 lines differ
- issue-tracker — 100% identical, 0 lines differ
- issue-tracker — 100% identical, 2 lines differ
- issue-tracker — 100% identical, 0 lines differ
- issue-tracker — 100% identical, 2 lines differ
- issue-tracker — 100% identical, 0 lines differ
- issue-tracker — 100% identical, 2 lines differ
- issue-tracker — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 46 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. 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
Used by /wayfinder. The map is a single issue with child issues as tickets.
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.
- yesterday First seen · 46 lines · 0 tokens per session scan A 52e9f9f1ec0f
issue-tracker is an agent published in the GitHub repository landing-ai/ade-cli (2,409 stars, last pushed 13d ago), licensed Apache-2.0. 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-30.
Other agents, from other repositories
release-runbook
Runbook operationnel pour publier une nouvelle version de Speekify.
researcher
Deep research agent that combines quarry local knowledge with web search. Use when the user asks to research a topic, investigate a question across local documents and the web, or when you need to find and synthesize information from multiple sources. Searches quarry first (local, fast, curated), then web for gaps.…
wiki-cartographer
High-altitude field synthesizer. Reads the compiled wiki/papers, wiki/concepts, and wiki/gaps trees and writes incremental updates to the field/ artifacts — shared assumptions, cross-paper tensions, topic saturation, and the problems.md candidate list — never touching ideas or novelty.
generic-agent
适用于任意本地 Agent，包括 Claude Code / Codex / 其他 CLI 编码 Agent。 通用能力契约见 adapter-contract.md。.
development-commands
Speekify turns CLI text, stdin, local .txt/.md/.pdf files and YouTube video transcripts or the readable content of a URL into a local WAV file.
hermes
本文件说明 Hermes 如何接入 douyin-agent-kit。通用能力契约见 adapter-contract.md；本文只写 Hermes 的具体做法。.