Borrowing it
Nothing to install: this file belongs to rome-os/rome. 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/rome-os/rome/main/.claude/skills/file-issue/SKILL.mdgit clone --depth 1 https://github.com/rome-os/romeWrote 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/rome-os/rome/file-issue)<a href="https://agentmods.dev/skills/rome-os/rome/file-issue"><img src="https://agentmods.dev/badge/skills/rome-os/rome/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.00094 | $0.01584 |
| Opus 5 | $0.00047 | $0.00792 |
| Sonnet 5 | $0.00019 | $0.00317 |
| Haiku 4.5 | $0.00009 | $0.00158 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File an issue
Goal end-state: one issue on the tracker whose type, title, body sections, and labels follow docs/authoring/github-issues.md and the rulebook of its type, with every required section filled from evidence.
The description arrives as the skill argument or in the conversation: $ARGUMENTS
The authoring docs own the issue format, and a rule there wins over any wording here. Read the shared rules first, then the rulebook of the type chosen in step 1:
- github-issues.md — title shape, the Situation section, the type labels.
- github-issues-bug-report.md
- github-issues-feature-request.md
- github-issues-task-spec.md
Prose in the title and body follows docs/authoring/WRITING.md. Situation uses the terms in docs/concepts/, and a term links to its entry on first use with a full https://github.com/<owner>/<repo>/blob/main/docs/concepts/<file>.md#<anchor> URL, because a relative link does not resolve inside an issue body.
1. Classify
Decide the type with the two questions from github-issues.md, in order:
- Does the system break its own intended behavior? → bug report.
- Is the change already decided and scoped? → task spec.
- Otherwise → feature request. A pain point with no feature attached, and a feature idea, both file as a feature request.
When the description supports two readings that change the type — a symptom the user may or may not consider intended behavior, or a change the user may or may not have decided — ask which one holds. Carry the question into step 3 rather than asking it alone.
2. Gather
Fill the required sections of the chosen type from three sources, in this order: the description, the tracker, the code. When step 1 left two readings open, gather what both readings need, so the answer in step 3 picks a draft rather than a second gather.
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 · 85 lines · 94 tokens per session scan A 7f2e39ba8dfa
file-issue is a skill published in the GitHub repository rome-os/rome (478 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 1,584 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
pm-assistant
Product operations assistant strategy contract. PM short answers and deep analysis should be evidence-grounded and should separate facts from hypotheses. Model calls, hooks, queueing, cancellation, notifications, and staged task execution stay in Rust.
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
meta-meeting-to-workflow
Use this meta-skill instead of answering directly when the user has meeting notes, transcripts, recordings, or rough discussion notes and wants them converted into decisions, owners, follow-ups, tasks, issues, or shareable minutes through multi-skill orchestration.
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.
meta-github-pr-watch-digest
Inspect the user's open GitHub PRs / failing CI / new issues via gh, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.
secretary
Workspace and research management — dispatch analyses, monitor running agents, manage workspaces and threads.