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 suyoumo/ClawProBench --skill github-workflowgit clone --depth 1 https://github.com/suyoumo/ClawProBenchWrote 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/suyoumo/clawprobench/github-workflow)<a href="https://agentmods.dev/skills/suyoumo/clawprobench/github-workflow"><img src="https://agentmods.dev/badge/skills/suyoumo/clawprobench/github-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/suyoumo/clawprobench/github-workflow"><img src="https://agentmods.dev/badge/skills/suyoumo/clawprobench/github-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.00045 | $0.00996 |
| Opus 5.5 | $0.00018 | $0.00398 |
| Sonnet 5.5 | $0.00009 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
github-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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow Automation
Install and maintain a complete issue-to-merge workflow for any GitHub repository. Maps GitHub webhook events and cron schedules into automated missions for planning, implementation, review, CI fixing, staging validation, and post-merge learning.
Workflow
- Gather project parameters from
projects/<owner>-<repo>/project.mdor ask the user. - Verify runtime prerequisites.
- Install or update mission set from templates.
- Run a dry test with
event_emit. - Monitor outcomes and tune prompts/filters.
Parameters
Read these from the project file in workspace, or collect from the user:
repository:owner/repo(required)maintainers: GitHub handles allowed to trigger implement/replan actionsstaging_branch: defaultstaging(or null if no staging workflow)main_branch: defaultmainbatch_interval_hours: default8
Prerequisites
Before installing missions, verify:
- GitHub skill authenticated (for issue/PR/comment/status operations).
- GitHub webhook delivery configured to
POST /webhook/tools/github. - Webhook HMAC secret configured in the secrets store as
github_webhook_secret. - Events can also be emitted via
event_emittool for testing.
Install Procedure
- Open
workflow-routines.md. - For each template block:
- Replace placeholders (
{{repository}},{{maintainers}}, branch names) - Namespace mission names with the repo slug (e.g.
wf-issue-plan-nearai-ironclaw) - Call
mission_createwithname,goal(the prompt), andcadence(cron expression orevent:<pattern>)
- Replace placeholders (
- If a mission already exists (check
mission_list), update rather than duplicate. - If
staging_branchis null, skipwf-staging-batch-review. - Write installation status to
projects/<owner>-<repo>/project.md. - Confirm install with
mission_list.
Mission Set
Install these missions per repository:
wf-issue-plan-<slug>: onissue.openedorissue.reopened, generate implementation plan comment.wf-maintainer-gate-<slug>: on maintainer comments, decide update-plan vs start implementation.wf-pr-monitor-<slug>: on PR open/sync/review-comment/review, address feedback and refresh branch.wf-ci-fix-<slug>: on CI status/check failures, apply fixes and push updates.wf-staging-review-<slug>: every N hours, review ready PRs, merge into staging, run batch correctness analysis, fix findings, then merge staging to main.wf-learning-<slug>: on merged PRs, extract mistakes/lessons and write to shared memory.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 104 lines · 45 tokens per session scan A 0e730ca5e2ed
github-workflow is a skill published in the GitHub repository suyoumo/ClawProBench (827 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 996 once invoked, about $0.0002 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
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
company-hr
Run HR for a PenguinHarness organization — guarantee every employee has an enabled calendar event, hire and offboard employees (channels included), evaluate and improve them (with the default-rsi-toolkit plugin's agent-optimization skill), and keep the handbook's role conventions current.
company-mirror
Run a PenguinHarness organization that mirrors a real company — one digital twin per real colleague, each twin's desk bound to that colleague's chat bot, twins answering what the handbook already knows and relaying the rest to one another instead of hiring, scheduling and filing tickets.
company-setup
Create a company-mode organization together with the user — collect its id, name, mission, shared workspace, model and CEO budget one question at a time, confirm the whole thing in one summary, then run penguin org create and hand the user over to company mode.
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.