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 workflowgit 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/workflow)<a href="https://agentmods.dev/skills/justinthomas2/agentrc/workflow"><img src="https://agentmods.dev/badge/skills/justinthomas2/agentrc/workflow/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/workflow"><img src="https://agentmods.dev/badge/skills/justinthomas2/agentrc/workflow.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.00030 | $0.00587 |
| Opus 5.5 | $0.00012 | $0.00235 |
| Sonnet 5.5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
workflow 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task
This skill is read-only. Run only:
git status -sbgh pr status
Do not branch, commit, push, post comments, edit files, or run mutating GitHub commands.
Pipeline Map
Print this compact map first, one line per skill:
file-issue: rough idea -> GitHub issue draft or filed issue; stops before filing for approval.work-issue: issue number -> local branch with committed implementation; stops before push or PR.open-pr: issue number -> pushed branch and opened PR; stops after reporting the PR URL.review-pr: PR number -> posted review feedback comment; stops before posting for approval.address-feedback: PR number -> committed review fixes; stops before push or reviewer replies.respond-feedback: PR number -> posted approved reviewer replies; ends the workflow.
State Detection
Use git status -sb to identify:
- current branch
- whether the branch is ahead of, behind, or diverged from its upstream
- whether there are uncommitted changes
Use gh pr status to identify:
- whether the current branch already has a PR
- the PR number when present
- whether the visible review decision is approved, changes requested, or review required
Then print:
- You are here: one concise sentence describing the current state.
- Next: the exact next skill invocation.
Choose the next invocation this way:
- On
mainwith no feature branch context:file-issuewith the rough idea. - On a non-main branch with uncommitted changes: finish or discard the local changes before invoking another pipeline skill.
- On a non-main branch with commits ahead of main and no PR:
open-prwith issue N. Infer N from a branch segment like16inrefactor/16-workflow-skill-names; if no issue number is clear, say that the issue number is needed. - On a branch with an open PR and no review decision yet:
review-prwith PR N to review it, or wait for an external review. - On a branch with an open PR and changes requested:
address-feedbackwith PR N. - After review-fix commits are ready on a PR branch:
respond-feedbackwith PR N once the fixes have been pushed and reviewed by Justin. - If the state is ambiguous, say what is missing instead of guessing.
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 · 58 lines · 30 tokens per session scan A 2aa4507289dc
workflow is a skill published in the GitHub repository JustinThomas2/agentrc (2 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 587 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.