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/shwilliamson/automatasaurus/github-workflownpx skills add shwilliamson/automatasaurus --skill github-workflowgit clone --depth 1 https://github.com/shwilliamson/automatasaurusWhat 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.00036 | $0.00872 |
| Opus 5 | $0.00018 | $0.00436 |
| Sonnet 5 | $0.00007 | $0.00174 |
| Haiku 4.5 | $0.00004 | $0.00087 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow Skill
Guidance for managing the development workflow through GitHub.
Issue State Labels
| Label | Description | When to Apply |
|---|---|---|
ready |
No blocking dependencies | Issue can be picked up |
in-progress |
Currently being implemented | Developer starts work |
blocked |
Waiting on dependencies | Has unresolved blockers |
needs-review |
PR open, awaiting reviews | PR created |
gh issue edit {n} --add-label "in-progress" --remove-label "ready"
gh issue edit {n} --add-label "needs-review" --remove-label "in-progress"
Dependency Tracking
In issue body:
## Dependencies
Depends on #12 (User authentication)
Depends on #15 (Database schema)
Parse dependencies:
gh issue view {n} --json body --jq '.body' | grep -oE "Depends on #[0-9]+" | grep -oE "[0-9]+"
gh issue view {dep} --json state --jq '.state'
Agent Identification
All GitHub interactions must include an agent identifier header.
Format: **[Agent Name]** at the start of every issue body, PR description, and comment.
Standardized Review Comments
Since all agents share the same GitHub user, reviews use standardized comments:
Approval:
✅ APPROVED - [Role]
[Summary]
Changes Requested:
❌ CHANGES REQUESTED - [Role]
[Issues to address]
Required Reviews Per PR
| Review | When Required |
|---|---|
| Architect | Always |
| Designer | If UI changes |
| Tester | Always |
Review Templates
Architect
gh pr comment {n} --body "**[Architect]**
✅ APPROVED - Architect
Clean architecture. LGTM."
Designer
gh pr comment {n} --body "**[Designer]**
✅ APPROVED - Designer
UI looks good. Accessibility met."
# Or if not applicable:
gh pr comment {n} --body "**[Designer]** N/A - No UI changes."
Tester
gh pr comment {n} --body "**[Tester]**
✅ APPROVED - Tester
**Tests:** All passing
**Manual:** Completed
Ready for merge."
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 · 162 lines · 36 tokens per session scan A fe1429f45d95
github-workflow is a skill published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 872 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…