Borrowing it
Nothing to install: this file belongs to dburkart/auto-engineer. 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/dburkart/auto-engineer/main/.claude/skills/file-issue/SKILL.mdgit clone --depth 1 https://github.com/dburkart/auto-engineerWrote 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/dburkart/auto-engineer/file-issue)<a href="https://agentmods.dev/skills/dburkart/auto-engineer/file-issue"><img src="https://agentmods.dev/badge/skills/dburkart/auto-engineer/file-issue/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/dburkart/auto-engineer/file-issue"><img src="https://agentmods.dev/badge/skills/dburkart/auto-engineer/file-issue.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.00988 |
| Opus 5.5 | $0.00024 | $0.00395 |
| Sonnet 5.5 | $0.00012 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
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 1mo 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
file-issue
Files a single GitHub issue against dburkart/auto-engineer with priority and classification labels applied on creation. Keeps the backlog triaged in one step instead of leaving un-labeled issues that pollute the auto-engineer candidate set.
Read docs/agent-playbooks/prioritization.md before running — the label taxonomy, priority rules, and triage policy all live there. This skill is the mechanical front-end for that policy.
Label taxonomy
Priority labels: priority:P0 (critical — blocks core functionality), priority:P1 (high — required for next milestone), priority:P2 (medium — polish and hardening), priority:P3 (low — nice-to-have or future work). Type labels: bug (something isn't working), enhancement (new feature or improvement). Every issue must have exactly one priority:* label and at least one type/area label.
When to invoke
- A merged PR surfaced out-of-scope follow-up work that needs its own issue (auto-engineer step 8, or a human reviewer deferring a nit).
- A
TODO/FIXMEwas introduced that deserves tracking. - The user says "file an issue for …" or invokes
/file-issuedirectly.
Do not use this skill to edit an existing issue — use mcp__github__update_issue for that.
Inputs
Either accept them as free-form arguments after /file-issue, or infer from the invoking context:
- title — imperative phrase, ≤ 72 chars, no emoji.
- motivation — 1–3 sentences on why this matters and what it unblocks.
- work — bulleted sub-tasks, concrete enough to act on cold in a week (file paths, type names, function signatures when known).
- context — relevant commit SHAs, file paths, existing issue numbers, or the PR that surfaced the follow-up.
If any of those are missing and cannot be reasonably inferred, skip the issue silently — do not ask the user. This skill may be called from auto-engineer or other agents where user interaction is not available; asking would block the loop.
Cycle
1. Dedupe
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.
- 1mo ago First seen · 98 lines · 61 tokens per session scan A c8624bca5e6c
file-issue is a skill published in the GitHub repository dburkart/auto-engineer (5 stars, last pushed 6mo ago), licensed BSD-3-Clause. It adds 61 tokens to every session and 988 once invoked, about $0.0002 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-31.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…