Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/HirogaKatageri/hirokatanpx agentmods add skills/hirogakatageri/hirokata/create-workflowWrote 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/hirogakatageri/hirokata/create-workflow)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/create-workflow"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/create-workflow.svg" alt="Measured on agentmods" 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.00113 | $0.02945 |
| Opus 5 | $0.00056 | $0.01473 |
| Sonnet 5 | $0.00023 | $0.00589 |
| Haiku 4.5 | $0.00011 | $0.00295 |
Grade A, and why
create-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 7d 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 — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Workflow
Interactively design and generate automation workflows — GitHub Actions pipelines, Python scripts, Node.js scripts, shell scripts, Makefiles, and more.
Purpose
Guide the user through designing a workflow by asking about their goal and preferred type, detecting the project's tech stack to suggest relevant steps, then generating a complete ready-to-use workflow file with sensible defaults.
Workflow
Step 1: Silently Scan the Project
Before asking the user anything, run these in parallel to detect context:
# Detect tech stack indicators
ls package.json requirements.txt Cargo.toml go.mod pom.xml build.gradle Gemfile pyproject.toml 2>/dev/null
# Check for existing workflows (avoid conflicts)
ls .github/workflows/ 2>/dev/null
# Check for existing scripts
ls Makefile scripts/ bin/ 2>/dev/null
Use the findings to:
- Pre-select sensible step suggestions (e.g.,
npm testfor Node,pytestfor Python) - Surface a warning if a similar workflow file already exists
- Inform file path suggestions in later steps
Step 2: Ask Core Questions
Use AskUserQuestion to ask both questions at once:
Question 1 — Goal:
"What do you want this workflow to accomplish?"
Examples: run tests on every PR, deploy to staging on push to main, lint code, build a Docker image, send a nightly report, sync data between services.
Question 2 — Workflow type:
| Option | Description |
|---|---|
| GitHub Actions | YAML pipeline triggered by push, PR, schedule, or manual dispatch |
| Python Script | Standalone .py script, optionally called from CI |
| Node.js Script | Standalone .js / .ts script, runnable with node |
| Shell / Bash Script | Portable .sh script for system or CI tasks |
| Makefile | make targets for local dev and CI tasks |
| Other | User describes a custom format |
Step 3: Gather Type-Specific Details
Based on the chosen type, ask follow-up questions with AskUserQuestion.
GitHub Actions
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.
- 7d ago First seen · 463 lines · 113 tokens per session scan A 220450269514
create-workflow is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed 3d ago), licensed MIT. It adds 113 tokens to every session and 2,945 once invoked, about $0.0006 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.