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/justinthomas2/agentrc/work-issuenpx skills add JustinThomas2/agentrc --skill work-issuegit clone --depth 1 https://github.com/JustinThomas2/agentrcWhat 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 | $0.00037 | $0.00449 |
| Opus 5 | $0.00018 | $0.00225 |
| Sonnet 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 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.
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.
- 2d 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 1mo ago), licensed MIT. It adds 37 tokens to every session and 449 once invoked, about $0.0002 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-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…