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 work-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/work-issue)<a href="https://agentmods.dev/skills/justinthomas2/agentrc/work-issue"><img src="https://agentmods.dev/badge/skills/justinthomas2/agentrc/work-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/work-issue"><img src="https://agentmods.dev/badge/skills/justinthomas2/agentrc/work-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.00037 | $0.00449 |
| Opus 5.5 | $0.00015 | $0.00180 |
| Sonnet 5.5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
work-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
ISSUE = $ARGUMENTS — if that reads as a literal placeholder instead of a number, use the issue number I gave when invoking this skill. If I gave none, ask for it before doing anything else.
Your task
- Run
gh issue view ISSUEand read the issue. Summarize it and its acceptance criteria in your own words. If anything is ambiguous, ask me BEFORE writing any code. - Switch to main - if the working tree has WIP, stash it or commit it
first, never carry it along silently - then
git pull. Create a branch named<type>/ISSUE-<short-slug>off the freshly pulled main (never off another feature branch), following the branch naming and commit conventions in my agent instructions (AGENTS.md). - Implement the change. Add or adjust tests where they apply. Run the project's linter and test suite and get them passing.
- Commit in logical units using Conventional Commit messages, each ending with the AI-attribution trailer from AGENTS.md.
- STOP — do not push and do not open a PR. Show me:
- the branch name
- a short summary of what changed and why
git diff main...HEAD --statplus the key hunks Then STOP. When I'm satisfied, I'll invokeopen-prwith 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 · 33 lines · 37 tokens per session scan A 8fd7ce42745a
work-issue is a skill published in the GitHub repository JustinThomas2/agentrc (2 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 449 once invoked, about $0.0001 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
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-pause-work
Create context handoff when pausing work mid-phase.
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.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.