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/byronxlg/skillfold/github-workflownpx skills add byronxlg/skillfold --skill github-workflowgit clone --depth 1 https://github.com/byronxlg/skillfoldWhat 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.00022 | $0.00474 |
| Opus 5 | $0.00011 | $0.00237 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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.
What it actually says
GitHub Workflow
You use GitHub as part of your development workflow, primarily through the gh CLI. You work with branches, pull requests, issues, and code review.
Branches and Pull Requests
- Create a feature branch for each unit of work:
git checkout -b <branch-name> - Keep branch names descriptive and lowercase with hyphens (e.g.,
fix-validation-error) - Open pull requests with a clear title and description:
gh pr create --title "..." --body "..." - View PR details:
gh pr view <number> - View PR diff:
gh pr diff <number> - Check CI status:
gh pr checks <number> - Merge approved PRs:
gh pr merge <number>
Code Review
- Review a PR by reading its diff:
gh pr diff <number> - Approve:
gh pr review <number> --approve --body "..." - Request changes:
gh pr review <number> --request-changes --body "..." - Comment without approval decision:
gh pr review <number> --comment --body "..." - View existing review comments:
gh api repos/{owner}/{repo}/pulls/{number}/comments
Issues
- List open issues:
gh issue list - View an issue:
gh issue view <number> - Create an issue:
gh issue create --title "..." --body "..." - Close an issue:
gh issue close <number> - Add labels:
gh issue edit <number> --add-label "bug"
Workflow
- Check for existing issues or PRs related to your work before starting
- Create a feature branch from the latest main branch
- Make focused commits with clear messages
- Push early and often to keep the remote up to date
- Open a PR when the work is ready for review
- Address review feedback with additional commits
- Merge after approval and passing CI checks
Output
Use gh commands to interact with GitHub. Prefer the CLI over the web interface for automation and reproducibility. Always verify CI status before merging.
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 · 49 lines · 22 tokens per session scan A e333bc5a3d6a
github-workflow is a skill published in the GitHub repository byronxlg/skillfold (12 stars, last pushed 9d ago), licensed MIT. It adds 22 tokens to every session and 474 once invoked, about $0.0001 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
audit-onboarding-proposal
Independently audit a brownfield onboarding transcript, operational map, or exact proposed documentation patch before application. Use when a fresh reviewer must verify an $onboard-repository first pass, distinguish environment-caused Unknowns from reasoning defects, score its safety and evidence gates, or run a…
engineering-wisdom
Provide an explicitly requested, repository-grounded engineering review using contextual heuristics for code clarity, SOLID and design, testing, refactoring, architecture, and professional practice. Use only when the user invokes $engineering-wisdom or explicitly asks for this installed engineering-wisdom pack; do not…
Artillery Load Testing
Modern cloud-scale load testing using Artillery.io for HTTP, WebSocket, Socket.io, and custom protocol testing with YAML-based test definitions.
red-team-adversarial
Adversarial security and resilience analysis — auto-triggered during /review and /test based on task classification. Provides attack surface analysis, boundary testing, auth bypass attempts, dependency chain attacks, and Beast Mode stress testing.
product-decision-agent
中文产品决策 Agent。用于中国大陆互联网产品、运营、增长、商业化、数据、项目推进和组织协作场景：产品规划、需求分析、PRD、需求优先级、排期、版本规划、Roadmap、MVP、灰度、上线、迭代、增长停滞、拉新、投放、渠道、裂变、CAC、LTV、ROI、留存、转化、DAU/MAU、GMV、漏斗、社区运营、内容供给、创作者、用户运营、活动运营、私域、会员、定价、指标异常、数据口径、埋点、A/B…
marketing-copy
Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be…