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 byronxlg/skillfold --skill github-workflowgit clone --depth 1 https://github.com/byronxlg/skillfoldWrote 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/byronxlg/skillfold/github-workflow)<a href="https://agentmods.dev/skills/byronxlg/skillfold/github-workflow"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/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/byronxlg/skillfold/github-workflow"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/github-workflow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00022 | $0.00474 |
| Opus 5.5 | $0.00009 | $0.00190 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 49 lines · 22 tokens per session scan A e333bc5a3d6a
github-workflow is a skill published in the GitHub repository byronxlg/skillfold (14 stars, last pushed 5d ago), licensed MIT. It adds 22 tokens to every session and 474 once invoked, about $0.0001 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
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
generate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
get-search-view-results
Get the current search results from the Search view in VS Code.
CreateCLI
Generates production-ready TypeScript CLIs via a 3-tier template system (manual arg parsing, Commander.js, oclif), each shipping full implementation, docs, package.json, strict config, JSON output, and exit-code compliance. USE WHEN create CLI, build CLI, command-line tool, wrap API, add command, upgrade tier…
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error. Also load when a live run you started for the user fails with an error from…
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.