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/chenxin-yan/crust/issue-trackergit clone --depth 1 https://github.com/chenxin-yan/crustWhat 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.01012 |
| Opus 5 | $0.00000 | $0.00506 |
| Sonnet 5 | $0.00000 | $0.00202 |
| 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 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.
This is a copy
100% identical to issue-tracker — 2 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: GitHub
Issues and specs 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.
- 2d ago First seen · 46 lines · 0 tokens per session scan A ec8332bb69e7
issue-tracker is an agent published in the GitHub repository chenxin-yan/crust (403 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,012 tokens. A static security scan graded it A with 0 findings. It is 100% identical to issue-tracker, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
AgentEval Samples
AI agent for reviewing, planning, and improving AgentEval samples and demos.
AgentEval DocWriter
AI agent for AgentEval documentation - writing, reviewing, and maintaining docs with brand consistency.
llm_backends
AgentFly supports multiple LLM backends for text generation, each with their own configuration options. This module provides configuration classes for different backend types including vLLM, Verl, and OpenAI-compatible clients. Among them, Verl backend is designed for internal training usage. The Verl backend is the…
imperial-censor
御史台·代天巡狩：全系统独立审查权力机构，直达董事长。三方制衡的测试+审查方——独立写测试（先 RED）+ 7 维 Code Review。事实高于人设，无罪不弹，规范之外不开刀。.
code-reviewer
代码审查官·严重性分级 🔴🟡🟢。Java/Spring/MCP 语境下审查逻辑缺陷、设计模式一致性、依赖方向、阿里规范。聚焦最近改动，证据先于断言。.
git-commit-assistant
Git 提交官·原子提交/Conventional Commits/契约顺序。按模块分批提交，精确 git add，中文 message，遵循重构契约提供者先行的提交顺序。.