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 skills add JustinThomas2/agentrc --skill file-issuegit clone --depth 1 https://github.com/JustinThomas2/agentrcWrote 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/justinthomas2/agentrc/file-issue)<a href="https://agentmods.dev/skills/justinthomas2/agentrc/file-issue"><img src="https://agentmods.dev/badge/skills/justinthomas2/agentrc/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/justinthomas2/agentrc/file-issue"><img src="https://agentmods.dev/badge/skills/justinthomas2/agentrc/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.00045 | $0.00546 |
| Opus 5.5 | $0.00018 | $0.00218 |
| Sonnet 5.5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
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 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.
What it actually says
IDEA = $ARGUMENTS — if that reads as a literal placeholder instead of a description, use the description I gave when invoking this skill. If I gave none, ask what the issue is about before doing anything else.
Issues drive the rest of the workflow: the work-issue skill reads them and
works from their acceptance criteria. A vague issue degrades everything
downstream, so the goal here is a draft concrete enough that work-issue can
act on it without guessing.
Your task
- Pin down the idea. If the scope, motivation, or acceptance criteria can't be determined from what I gave, ask me BEFORE drafting — don't pad thin input into an official-looking issue.
- Check for duplicates with
gh issue listandgh search issues(read-only). If a near-match exists — open or recently closed — show it to me and ask whether to proceed, extend that issue instead, or drop it. Never file over an existing issue. - Draft the issue in this shape:
- Title — imperative and specific
- Problem — why this matters, what breaks or is missing today
- Proposal — the intended change, concrete enough to implement
- Guardrails — constraints and non-goals; omit if none apply
- Acceptance criteria — a
- [ ]checklist of verifiable outcomes thework-issueskill can work from and check off - End the body with the AI-attribution footer from AGENTS.md as its last line.
- STOP — show me the full draft (title and body) and wait for my approval. Revise per my feedback until I approve.
- Only after approval, file it with
gh issue create. (This will ask for my approval — that is intentional; wait for it.) - Reply with the issue URL. Then STOP. When I'm satisfied, I'll invoke
work-issuewith issue N.
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 First seen · 43 lines · 45 tokens per session scan A 7dce787e1a3a
file-issue is a skill published in the GitHub repository JustinThomas2/agentrc (2 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 546 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.
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)…
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…