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/zfinix/aster/gh-pr-workflownpx skills add Zfinix/aster --skill gh-pr-workflowgit clone --depth 1 https://github.com/Zfinix/asterWrote 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/zfinix/aster/gh-pr-workflow)<a href="https://agentmods.dev/skills/zfinix/aster/gh-pr-workflow"><img src="https://agentmods.dev/badge/skills/zfinix/aster/gh-pr-workflow.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00357 |
| Opus 5 | $0.00023 | $0.00179 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
gh-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 4d 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
GitHub PR workflow
- Use
ghfor GitHub operations. Structured queries beat scraping:gh pr view 12 --json title,body,files,comments,gh pr checks 12,gh issue list --limit 10. - Big diffs go to a file, not the conversation.
gh pr diff 12 > /tmp/pr12.diff, then search and read slices of that file. Never print a whole PR diff into the chat. - Draft first, post on approval. Write the review or comment body to a
scratch file, show it to the user, and only after they approve post it:
gh api repos/{owner}/{repo}/pulls/12/reviews --method POST --input review.json. Never post to GitHub as a side effect of being asked to "review". - One PR at a time, one comment per issue found. Do not batch several PRs' feedback into one pass, and do not stack multiple problems into one comment.
- Auth errors are a full stop. A 401 or
gh auth statusfailure means tell the user to rungh auth login. Retrying, or switching to raw git pushes, will not help. - PR bodies: summary plus test plan. Short paragraphs over prose walls. No attribution footers unless asked.
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.
- 4d ago First seen · 26 lines · 46 tokens per session scan A eae7b3106da4
gh-pr-workflow is a skill published in the GitHub repository Zfinix/aster (43 stars, last pushed 2d ago), licensed Apache-2.0. It adds 46 tokens to every session and 357 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-30.
Other skills, from other repositories
new-plugin
Factory line for adding a new HAR verification plugin (like playwright or rocketsim) for any framework — research the framework docs, build the template under src/templates/plugins/, register it everywhere, validate on a real repository, and open a PR. Use when asked to add/create a plugin, plugin template, or…
factory-line
Factory line for executing one station of a declared multi-station program — read the installed line bundle (har line status), plan parallel work into isolated HAR slots, run the cumulative gate with har line gate, and hand off for human review. Use when asked to "run a factory line", "run the next station", "execute…
v1-milestone
Factory line for executing one milestone of the HAR v1.0.0 refactor (epic os-factory/har#225) — plan the wave of parallel subagents, implement each issue in its own HAR slot, ship stacked PRs, run the fixture-e2e milestone gate, and hand off for review. Use when asked to "run the next v1 milestone", "work on v1.0.0"…
lemma-user
Operate an existing Lemma pod from the CLI as a human or agent: inspect resources, query tables and records under RLS, search and read pod files (converted markdown, page images), run functions and workflows, submit waiting workflow forms, chat with pod agents, message pod members, and execute third-party connector…
lemma-builder
Design and build complete Lemma pods: model tables/files/functions/agents/workflows/schedules/connectors/surfaces/apps from a problem statement, author a local pod bundle, import progressively with the Lemma CLI, and verify every layer. Use for pod design, creation, restructuring, import/export, and app development.…
lemma-evals
Design, run, and review repeatable evaluations for Lemma agents, functions, and workflows. Use when defining evaluation contracts and case datasets, comparing a baseline with a candidate revision or runtime, checking deterministic correctness or rubric-scored judgment, measuring repeated-run variance, testing…