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 skills/sma1lboy/rove/file-issuenpx skills add Sma1lboy/rove --skill file-issuegit clone --depth 1 https://github.com/Sma1lboy/roveWrote 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/sma1lboy/rove/file-issue)<a href="https://agentmods.dev/skills/sma1lboy/rove/file-issue"><img src="https://agentmods.dev/badge/skills/sma1lboy/rove/file-issue.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.1 | $0.00184 | $0.02326 |
| Opus 5 | $0.00092 | $0.01163 |
| Sonnet 5 | $0.00037 | $0.00465 |
| Haiku 4.5 | $0.00018 | $0.00233 |
Grade A, and why
file-issue 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 6d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File a GitHub issue
Turn a rough idea, bug report, or low-priority task into a well-structured GitHub
issue and file it with gh. The output should be something an outside contributor
can pick up cold — accurate file pointers, clear scope, explicit acceptance — not a
one-line stub.
Scope boundary (read first)
Rove tracks its own work in the daemon-owned issue store (rove api issue-*, the
web Issues page) — see docs/WORK-TRACKING.md. That
is the default for internal backlog.
This skill is for outward-facing GitHub issues — work you intend to hand to
external contributors (especially good first issues), or a public bug report. If the
user just wants to jot down internal backlog, prefer the daemon store and say so. If
they explicitly want a GitHub issue, proceed here.
Modes
The skill handles three shapes of input — detect which from the user's ask:
- Single — one idea / bug → one issue. Draft it, auto-classify (Step 1), confirm, file. The lightest path; fine to file directly once the draft + labels are shown.
- Batch — a list of ideas / a backlog dump / "file these N as issues" → many issues. Draft all, classify each, present the whole set as a table (title + proposed labels) for one confirmation, then file them in a loop and report URLs together.
- From unsolved problems — the user points at problems that came up but weren't
fixed this session ("发没解决的上去") — e.g. a known bug you hit, a deferred follow-up,
a TODO you found. Convert each into an issue: capture the symptom/repro while it's
fresh, mark it
bugorenhancement, and note in the body that it's filed-not-fixed (no implied owner). Then batch-confirm and file as above.
Pick the mode, then follow the per-issue steps below for each issue.
Hard rules (non-negotiable)
- Filing is an outward-facing publish. Draft first, then confirm the set before
gh issue create— don't create silently. Editing an already-filed issue is fine without re-asking. - No AI / Anthropic / Claude / Codex attribution anywhere in the title, body, or comments (per CLAUDE.md). No "Generated with…" footers.
- Never invent file paths, line numbers, flags, or function names. Every pointer in the body must be verified against the current tree (see Step 2). A wrong pointer costs a contributor 30–50% of their session reconciling a false premise.
- Default language: English for issue titles and bodies (the repo's contributor language), even when the conversation is in Chinese. Narrate to the user in whatever language they're using. If the user asks for another language, follow that.
- One concern per issue. If an idea bundles several independent tasks, split it into several issues (e.g. "add a theme" is one issue per theme).
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.
- 6d ago First seen · 202 lines · 184 tokens per session scan A d4b28546a142
file-issue is a skill published in the GitHub repository Sma1lboy/rove (116 stars, last pushed today), licensed MIT. It adds 184 tokens to every session and 2,326 once invoked, about $0.0009 per session on Opus 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.
Other skills, from other repositories
omd-grill
锁 plan/SDD 前的对抗式审问:沿决策树走、先给推荐答案、事实自查·技术 Decision 自裁·真 owner 岔口才阻塞问、对标外部实现逼问「为何偏离」;宽解岔口就地开 council;产决策记录表喂 /omd-contract。审议纪律:只讨论不动手。Trigger:/omd-grill、审问、盘问这个方案、把这事讨论清楚、压测计划、stress-test。.
vf-security-checklist
Use when touching auth, user input validation, file paths, redirects, WebSocket, uploads, rate limiting, CORS, or any security-sensitive code in veryfront.
scaffold-ai-app
Scaffold a Veryfront app with AI tools, agent definitions, and knowledge base.
debug-build
Diagnose and fix build failures using structured error output.
omd-council
多视角专家议会:宽解空间的设计/决策问题,经 omd dagresearch(council 模式)并行多 persona 出方案 + 多 lens 择优;领域岔口走接地档(反 happy-path)。Trigger:/omd-council、开会审议、多方案对比、给我几个选项、拿不准选哪个。.
omd-deliver
执行 omd pathfinder 已散尽区域(编译 slice → 跑 DAG 真改文件 → 票翻 delivered),标 delivered 前逐票核对真身(delivered✅≠东西真在)。deliberate/build 的权力闸,仅 owner 明令。Trigger:/omd-deliver、交付、开始执行、动手吧。.