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 baseballyama/eslint-plugin-postgresql --skill pr-workflowgit clone --depth 1 https://github.com/baseballyama/eslint-plugin-postgresqlWrote 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/baseballyama/eslint-plugin-postgresql/pr-workflow)<a href="https://agentmods.dev/skills/baseballyama/eslint-plugin-postgresql/pr-workflow"><img src="https://agentmods.dev/badge/skills/baseballyama/eslint-plugin-postgresql/pr-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/baseballyama/eslint-plugin-postgresql/pr-workflow"><img src="https://agentmods.dev/badge/skills/baseballyama/eslint-plugin-postgresql/pr-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.01711 |
| Opus 5.5 | $0.00025 | $0.00684 |
| Sonnet 5.5 | $0.00013 | $0.00342 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
pr-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 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR workflow
The shape of a PR communicates the change to maintainers and to a future archaeologist
reading git log. Get it right at write time — the cost of fixing a confusing PR
later is much higher than getting it right once.
Before you open the PR
- Branch is up to date with the base. Rebase onto
main(or whatever the base is) so the PR diff is clean. Don't mergemaininto your feature branch as a habit; rebase. - All quality gates pass locally. Use the
run-check-and-testskill — typecheck, lint, format, test, build. CI will catch you if you skip this; just do it locally. - Each commit is meaningful. Squash WIP commits. The git log should read as a sequence of "I did this, then I did this, then I did this," not "fix typo / fix again / really fix this time."
- The change has an issue or design discussion to point at, unless it's trivially small (typo, comment, single-line bugfix). For non-trivial features, the discussion happens before the PR, not in PR review.
Branch name
<type>/<short-slug>
Conventional types match the commit prefixes below: feat, fix, refactor, docs,
test, chore, perf, ci, build. If the work resolves a specific issue, include
the number: fix/issue-123-empty-sheet-crash.
PR title
Use Conventional Commits prefixes — they drive the changelog and make scanning history easy.
<type>(<optional-scope>)<!?>: <imperative summary>
| Prefix | When to use |
|---|---|
feat |
New user-visible capability |
fix |
Bug fix |
refactor |
Internal change with no user-visible behavior change |
perf |
Performance improvement |
docs |
Documentation only |
test |
Tests only |
build |
Build system, dependencies |
ci |
CI configuration |
chore |
Tooling, repo plumbing |
revert |
Reverting a previous commit |
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 · 192 lines · 63 tokens per session scan A 9ca6c5b1c6a1
pr-workflow is a skill published in the GitHub repository baseballyama/eslint-plugin-postgresql (11 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,711 once invoked, about $0.0003 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-30.
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.