Borrowing it
Nothing to install: this file belongs to githubnext/gh-aw-workshop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/githubnext/gh-aw-workshop/main/.github/skills/agentic-workflows/SKILL.mdgit clone --depth 1 https://github.com/githubnext/gh-aw-workshopWrote 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/githubnext/gh-aw-workshop/agentic-workflows)<a href="https://agentmods.dev/skills/githubnext/gh-aw-workshop/agentic-workflows"><img src="https://agentmods.dev/badge/skills/githubnext/gh-aw-workshop/agentic-workflows/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/githubnext/gh-aw-workshop/agentic-workflows"><img src="https://agentmods.dev/badge/skills/githubnext/gh-aw-workshop/agentic-workflows.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.00020 | $0.01333 |
| Opus 5.5 | $0.00008 | $0.00533 |
| Sonnet 5.5 | $0.00004 | $0.00267 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
agentic-workflows 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 Changed · +15 lines · -1 tokens per session 0c0ed35d9f5b
- 1mo ago First seen · 98 lines · 21 tokens per session scan A c274b06e0e82
agentic-workflows is a skill published in the GitHub repository githubnext/gh-aw-workshop (56 stars, last pushed today), with no licence file. It adds 20 tokens to every session and 1,333 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
resolve-pr-feedback
Use when asked to resolve, address, fix, or reply to review feedback on a GitHub Pull Request or GitLab Merge Request, including review comments, unresolved threads, requested changes, or "apply the review comments" requests.
prepare-ticket
Use when asked whether a ticket or issue is ready for development, or to prepare, validate, refine, challenge, or sanity-check a Jira work item, GitHub Issue, or GitLab Issue before building it. Checks material claims against evidence, follows questions until outcome decisions are settled, rewrites the title and…
review-pr
Use when asked to review a GitHub Pull Request or GitLab Merge Request, including PR/MR URLs, identifiers, discussions, findings, inline comments, approvals, or request-changes actions.
code-review
Reusable review core for structured findings on supplied code or diffs. Invoked by review-pr, review-local, and the pre-push self-review in resolve-pr-feedback; not for reviewing a PR/MR or local working tree directly, use those skills instead.
implement-ticket
Use when asked to implement, build, or pick up a ticket end to end — a Jira work item, GitHub Issue, or GitLab Issue — including "implement ABC-123", "implement gh issue #137", "work on issue 137", or "pick up this ticket". Critiques the request against the code, builds it in a throwaway git worktree, verifies it with…
review-architecture
Read-only architecture and design-quality review of an existing codebase. Finds hot spots from git churn, file growth, complexity and files that change together, then checks them against layering, dependency direction, cohesion, SOLID, simplicity, test safety and platform-support rules (runtime and framework end of…