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 zircote-plugins/github-agentic-workflows --skill aw-authorgit clone --depth 1 https://github.com/zircote-plugins/github-agentic-workflowsWrote 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/zircote-plugins/github-agentic-workflows/aw-author)<a href="https://agentmods.dev/skills/zircote-plugins/github-agentic-workflows/aw-author"><img src="https://agentmods.dev/badge/skills/zircote-plugins/github-agentic-workflows/aw-author/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/zircote-plugins/github-agentic-workflows/aw-author"><img src="https://agentmods.dev/badge/skills/zircote-plugins/github-agentic-workflows/aw-author.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.00091 | $0.04941 |
| Opus 5.5 | $0.00036 | $0.01976 |
| Sonnet 5.5 | $0.00018 | $0.00988 |
| Haiku 4.5 | $0.00009 | $0.00494 |
Grade A, and why
aw-author scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
27. **MCP server stdout breaks initialization** — any stdout before the JSON-RPC handshake breaks the MCP gateway; redirect all `apk add`, `pip install`, `curl` output to `/dev/null` How it starts
The opening of the file, as written. The whole thing — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Agentic Workflow Author
You are an expert in GitHub Agentic Workflows (gh-aw) — a system that uses markdown files with YAML frontmatter to define agentic automation compiled into GitHub Actions via gh aw compile.
Mode Detection
Determine the user's intent and route to the appropriate mode:
| User Intent | Mode | Trigger Phrases |
|---|---|---|
| Create a new workflow from scratch | Interactive | "new", "create", "write", "build" |
| Generate a workflow from a description | Generate | "generate", "one-shot", "quick" |
| Check an existing workflow for errors | Validate | "validate", "check", "verify", "lint" |
| Improve an existing workflow | Improve | "improve", "optimize", "refine", "review" |
| Debug a failing workflow | Debug | "debug", "fix", "broken", "failing", "error" |
| Ask about the spec or features | Query | Any question about gh-aw capabilities |
If the mode is ambiguous, ask the user:
AskUserQuestion: "What would you like to do with your gh-aw workflow?"
Options:
- "Create new workflow (guided)" → Interactive mode
- "Generate from description (one-shot)" → Generate mode
- "Validate existing workflow" → Validate mode
- "Improve existing workflow" → Improve mode
- "Debug a failing workflow" → Debug mode
Interactive Mode (Guided Authoring)
Walk the user through building a workflow step by step using AskUserQuestion at each phase.
Phase 1: Purpose & Trigger
AskUserQuestion: "What should this workflow do?"
→ Free text description
AskUserQuestion: "What triggers this workflow?"
Options:
- "New/updated issues" → on.issues
- "New/updated pull requests" → on.pull_request
- "Issue/PR comments (slash commands)" → on.issue_comment
- "Scheduled (cron/daily)" → on.schedule
- "Manual dispatch" → on.workflow_dispatch
- "Push to branch" → on.push
- "Discussion events" → on.discussion
For event-triggered workflows (issues, PRs, comments, discussions), always include reaction: eyes in the on: block. This grants the compiler permissions for pre_activation.
What ships with it
9 files 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.
- references/examples.md 8.8 KB
- references/frontmatter-schema.md 62 KB
- references/llms-resources.md 3.5 KB
- references/markdown-body.md 9.2 KB
- references/orchestration.md 8.0 KB
- references/production-gotchas.md 16 KB
- references/safe-outputs.md 28 KB
- references/tools-reference.md 15 KB
- references/validation.md 15 KB
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 · 431 lines · 91 tokens per session scan A d3c3c0bf875e
aw-author is a skill published in the GitHub repository zircote-plugins/github-agentic-workflows (2 stars, last pushed 3mo ago), licensed MIT. It adds 91 tokens to every session and 4,941 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
github-actions
Use when authoring or fixing GitHub Actions CI/CD — workflows under .github/workflows, triggers, job matrix, caching, token permissions, OIDC cloud deploys, environment gates, reusable workflows. NOT the Dockerfile or image build strategy (that is docker), NOT the branching model (that is git-workflow), NOT release…
ci-cd
Build and repair reproducible CI and deployment workflows with explicit artifacts, permissions and release gates. Use when working on GitHub Actions or other pipelines, caches, matrices, packaging or deployment evidence; preserve the authoritative checks and never hide failures.
renovate
Generate renovate.json covering all dependency file types used in a repo, emit a GitHub Actions workflow that validates renovate.json on every PR, or generate a pre-commit hook for local validation.
zizmor
Audit GitHub Actions workflows, composite actions, Dependabot configs, and pre-commit configs for security findings using zizmor — template injection, credential persistence, unpinned uses, over-broad permissions, impostor commits. Covers local CLI, auto-fix, zizmor.yml policy, severity-based CI gates, SARIF upload…
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.