RocketMQ-Rust is a Rust reimplementation of Apache RocketMQ, a distributed message-queue system for sending and processing messages between applications. It is for Rust developers who need messaging middleware compatible with the RocketMQ protocol.
Borrowing it
Nothing to install: this file belongs to mxsm/rocketmq-rust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mxsm/rocketmq-rust/main/.agents/skills/rocketmq-rust-issue-generator/SKILL.mdgit clone --depth 1 https://github.com/mxsm/rocketmq-rustWrote 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/skills/mxsm/rocketmq-rust/rocketmq-rust-issue-generator)<a href="https://agentmods.dev/skills/mxsm/rocketmq-rust/rocketmq-rust-issue-generator"><img src="https://agentmods.dev/badge/skills/mxsm/rocketmq-rust/rocketmq-rust-issue-generator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mxsm/rocketmq-rust/rocketmq-rust-issue-generator"><img src="https://agentmods.dev/badge/skills/mxsm/rocketmq-rust/rocketmq-rust-issue-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 88 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.1 | $0.00102 | $0.01447 |
| Opus 5.5 | $0.00041 | $0.00579 |
| Sonnet 5.5 | $0.00020 | $0.00289 |
| Haiku 4.5 | $0.00010 | $0.00145 |
Grade A, and why
rocketmq-rust-issue-generator 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RocketMQ Rust Issue Generator
Generate GitHub issue drafts from the repository's real issue forms. Template-driven — do not output a fixed canonical body unless the selected form has those fields.
When the repository owner or maintainer wants to prepare issues for new contributors to claim, also use rocketmq-rust-good-first-issue for concrete file checklists, newcomer labels, and optional per-crate sub-issues.
When to Use
- User asks to create, draft, or publish a GitHub issue for rocketmq-rust
- User's rough draft mentions generic sections or non-existent template names — must be converted to real forms
- Issue must preserve exact template title prefix (including emoji), label set, and field order
- Local filesystem paths must be audited and removed before publishing
- Public issue titles and body content must be English-only
When NOT to use: Non-rocketmq-rust repositories, pure discussion/questions that should not become GitHub issues, or requests where the user explicitly says not to apply issue templates.
Quick Reference
| Intent | Template | Title Prefix |
|---|---|---|
| Bug, panic, incorrect behavior | bug_report.yml |
[Bug🐛] |
| Missing/improved test coverage | unit_test.yml |
[Test🧪] |
| Docs, README, examples, comments | doc.yml |
[Doc📝] |
| New broker/client/store/dashboard capability | feature_request.yml |
[Feature🚀] |
| CI gate, runtime audit, ergonomics | enhancement_request.yml |
[Enhancement✨] |
| Internal restructure, module cleanup | refactor.yml |
[Refactor♻️] |
Select the narrowest template. When ambiguous, state tradeoff and choose narrowest (e.g., "add consume queue recovery tests" → unit test, not feature). Verify files exist in checkout — don't assume draft-only names like architecture.yml.
Workflow
1. Locate Templates
rg --hidden --files -g '.github/ISSUE_TEMPLATE/**' -g 'ISSUE_TEMPLATE/**' -g '!**/target/**'
Read config.yml for policy. For each form, extract name, title prefix (with emoji), labels, every body item in order, and validations.required. For Markdown forms, preserve heading order and checklist meaning.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago Changed · +2 lines ae78b68f7b8c
- 2mo ago First seen · 110 lines · 102 tokens per session scan A 2749328960b2
rocketmq-rust-issue-generator is a skill published in the GitHub repository mxsm/rocketmq-rust (1,538 stars, last pushed today), licensed Apache-2.0. It adds 102 tokens to every session and 1,447 once invoked, about $0.0004 per session on Opus 5.5. 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.
rocketmq-rust-issue-generator compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rocketmq-rust-issue-generatormxsm/rocketmq-rust | Skill | 1.5k | today | Apache-2.0 | A | 102 | Claude Code, Codex |
| hotpath_cloudpawurb/hotpath-rs | Skill | 1.9k | 19d ago | MIT | A | 110 | Claude Code |
| ak-testyaalalabs/agent-kernel | Skill | 192 | yesterday | Apache-2.0 | A | 47 | Claude Code, Codex |
| hotpath_init_ci_forkspawurb/hotpath-rs | Skill | 1.9k | 19d ago | MIT | B | 95 | Claude Code |
| hotpath_init_cipawurb/hotpath-rs | Skill | 1.9k | 19d ago | MIT | B | 98 | Claude Code |
| test-rustd-oit/rust-2026-template | Skill | 15 | yesterday | MIT | A | 63 | Claude Code, Codex |
| systematic-debuggingDDS-Solutions/AI-TadPole-OS | Skill | 8 | yesterday | MIT | A | 33 | Claude Code |