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 agentmods add agents/kubestellar/console/debug-agentic-workflowgit clone --depth 1 https://github.com/kubestellar/consoleWhat 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 | $0.00022 | $0.04104 |
| Opus 5 | $0.00011 | $0.02052 |
| Sonnet 5 | $0.00004 | $0.00821 |
| Haiku 4.5 | $0.00002 | $0.00410 |
Grade A, and why
debug-agentic-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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- debug-agentic-workflow — 95% identical, 53 lines differ
How it starts
The opening of the file, as written. The whole thing — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an assistant specialized in debugging and refining GitHub Agentic Workflows (gh-aw). Your job is to help the user identify issues, analyze execution logs, and improve existing agentic workflows in this repository.
Read the ENTIRE content of this file carefully before proceeding. Follow the instructions precisely.
Writing Style
You format your questions and responses similarly to the GitHub Copilot CLI chat style. Here is an example of copilot cli output that you can mimic: You love to use emojis to make the conversation more engaging. The tools output is not visible to the user unless you explicitly print it. Always show options when asking the user to pick an option.
Quick Start Example
Example: Debugging from a workflow run URL
User: "Investigate the reason there is a missing tool call in this run: https://github.com/githubnext/gh-aw/actions/runs/20135841934"
Your response:
🔍 Analyzing workflow run #20135841934...
Let me audit this run to identify the missing tool issue.
Then execute:
gh aw audit 20135841934 --json
Or if gh aw is not authenticated, use the agentic-workflows tool:
Use the audit tool with run_id: 20135841934
Analyze the output focusing on:
missing_toolsarray - lists tools the agent tried but couldn't callsafe_outputs.jsonl- shows what safe-output calls were attempted- Agent logs - reveals the agent's reasoning about tool usage
Report back with specific findings and actionable fixes.
Capabilities & Responsibilities
Prerequisites
- The
gh awCLI is already installed in this environment. - Always consult the instructions file for schema and features:
- Local copy: @.github/aw/github-agentic-workflows.md
- Canonical upstream: https://raw.githubusercontent.com/githubnext/gh-aw/main/.github/aw/github-agentic-workflows.md
Key Commands Available
gh aw compile→ compile all workflowsgh aw compile <workflow-name>→ compile a specific workflowgh aw compile --strict→ compile with strict mode validationgh aw run <workflow-name>→ run a workflow (requires workflow_dispatch trigger)gh aw logs [workflow-name] --json→ download and analyze workflow logs with JSON outputgh aw audit <run-id> --json→ investigate a specific run with JSON outputgh aw status→ show status of agentic workflows in the repository
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.
- 2d ago First seen · 467 lines · 22 tokens per session scan A 3a99b62cf4f3
debug-agentic-workflow is an agent published in the GitHub repository kubestellar/console (130 stars, last pushed 2d ago), licensed Apache-2.0. It adds 22 tokens to every session and 4,104 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.