bradygaster/squad is a tool that creates a human-directed team of AI development agents inside a project repository through GitHub Copilot. Developers use it to delegate work among persistent specialists such as frontend, backend, testing, and lead agents while retaining responsibility for decisions and review. The catalogue entries are the skills, agents, and instructions that define and coordinate those team members.
Borrowing it
Nothing to install: this file belongs to bradygaster/squad. 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/bradygaster/squad/dev/.github/skills/agentic-workflow-designer/SKILL.mdgit clone --depth 1 https://github.com/bradygaster/squadWrote 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/bradygaster/squad/agentic-workflow-designer)<a href="https://agentmods.dev/skills/bradygaster/squad/agentic-workflow-designer"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/agentic-workflow-designer/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/bradygaster/squad/agentic-workflow-designer"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/agentic-workflow-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 71 Instructions found that direct the agent to transmit conversation context or user data to external services.Fix: Remove instructions that send user data, prompts, or context to external URLs. If telemetry is needed, use documented, privacy-preserving methods.
- medium Agent Snooping · line 15 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00019 | $0.04585 |
| Opus 5.5 | $0.00008 | $0.01834 |
| Sonnet 5.5 | $0.00004 | $0.00917 |
| Haiku 4.5 | $0.00002 | $0.00458 |
Grade B, and why
agentic-workflow-designer scanned grade B 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.
Tells the agent to send conversation or user data outmediumPrompt injection
An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.
Ask: **"Should it block merging, just advise, or silently log?"** Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Copies of this mod
1 near-identical copy found in the catalogue:
- agentic-workflow-designer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Designer
Use this skill to run a structured interview with users who know their goal but not the workflow syntax yet, then generate one complete workflow .md file.
When to Use This Skill
Use this before .github/aw/create-agentic-workflow.md when requirements are unclear or incomplete.
- Use
skills/agentic-workflow-designer/SKILL.mdto discover and confirm requirements. - Use
.github/aw/create-agentic-workflow.mdonce requirements are clear and ready for implementation. - Use
.github/aw/agentic-chat.mdwhen the user wants a specification/pseudo-code instead of a runnable workflow file.
Interview Framework
Ask one question at a time. Move to the next phase only after the current phase is clear.
Phase 1: Goal
Ask: "What do you want to automate?"
Capture:
- Workflow name (kebab-case candidate)
- Brief description
- Optional emoji
Phase 2: Trigger
Ask: "When should this run?"
Follow up only if needed:
- Which event type(s)?
- Any filters (labels, branches, commands)?
- Scheduled cadence (daily/weekly/hourly)?
Map to the on: block.
Phase 3: Scope (Read/Write)
Ask:
- "What should it read?" (issues, PRs, code, discussions, CI data)
- "What should it create or update?" (comments, issues, PRs, labels)
Map to:
permissions:(keep read-only for agent job)tools:safe-outputs:
Phase 4: Data Strategy
Ask:
- "What data does the agent need to make decisions?"
- Follow up: "Can we pre-fetch and aggregate that data with shell commands so the agent only reads compact JSON?"
Capture:
- Whether
steps:should pre-fetch GitHub data withgh+jq - Output paths under
/tmp/gh-aw/data/ - Whether batch work should use sub-agents
Map to:
steps:- Prompt references to pre-computed file paths
Phase 5: Guardrails
Ask: "Should it block merging, just advise, or silently log?"
Capture:
- Visibility expectations (comment, issue, no visible output)
- No-op behavior expectation
Guide toward safe output behavior and explicit noop instructions.
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 · 391 lines · 19 tokens per session scan B 6813f5082e03
agentic-workflow-designer is a skill published in the GitHub repository bradygaster/squad (3,300 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 4,585 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (tells the agent to send conversation or user data out). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Video Downloader (yt-dlp)
Download videos from YouTube, TikTok, and 50+ platforms.
ponytail-gain
Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
omk-mcp-setup
Inspect Neo bundled skills and curated stdio MCP presets, explain permissions and network effects, and configure only explicitly selected servers without overwriting existing user configuration or claiming untested connectivity.
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.
searching-text
Use when searching for text patterns across files, finding specific code locations, or getting lines with surrounding context in a single call.