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/sflandergan/agentic-coding/agent-workflow-extensiongit clone --depth 1 https://github.com/sflandergan/agentic-codingWhat 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.00000 | $0.00552 |
| Opus 5 | $0.00000 | $0.00276 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
agent-workflow-extension 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 yesterday.
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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Workflow Extension Guide
Use this guide when changing coding assistant workflows, agents, or reusable skills.
Boundaries
docs/agents/*.mdfiles are role loading/reference contracts. Keep them focused on which repository docs an agent must load for a workflow. Do not put detailed executable workflow behavior there..opencode/agents/*.mdfiles define OpenCode agent behavior, permissions, default workflow, escalation rules, and tool usage..claude/skills/*/SKILL.mdfiles define Claude skill behavior for the matching workflow..agents/skills/*files provide reusable mechanics shared by workflows. They may describe how to use bundled scripts or helpers, but they should not own role-level orchestration for review-plan, review-code, planner, implement, or finish workflows.
GitHub PR comment workflow boundary
- The
github-pr-commentsskill owns reading PR comments, classifying comment target types, obtaining exact IDs, and posting approved replies through project scripts. - Review agents own deciding what the comments mean, validating technical claims, combining them with independent review findings, suggesting fixes, and requesting approval before edits or replies.
Default placement rules
- If the change says what a role should do by default, update the matching
.opencode/agents/*.mdand.claude/skills/*/SKILL.mdfiles. - If the change says which docs a role must load, update the matching
docs/agents/*.mdfile. - If the change says how to run a shared helper script or avoid helper-specific mistakes, update the matching
.agents/skills/*file. - If a workflow change affects both OpenCode and Claude, update both definitions in the same plan and verify they remain aligned.
Agent and skill references
- OpenCode. Agents are invoked with
@agentnamein thetasktool (e.g.,@explore). A workflow agent may dispatch@explore, but should not name other workflow agents (e.g.,@brainstorm,@planner) in its body — cross-workflow hand-offs are the user's responsibility. - Claude Code. Skills are invoked by the user with
/skillname. Subagents are dispatched via the Agent tool by name with a leading@(e.g.,@explore). A workflow skill should not name other workflow skills (e.g.,/brainstorm,/planner) or OpenCode agents (e.g.,@implement) in its body. - Shared skills (under
.agents/skills/) provide reusable mechanics — wrappers, scripts, methodology — and may be referenced by /name because they are not workflow orchestration.
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.
- yesterday First seen · 29 lines · 0 tokens per session scan A 21ec7c6da599
agent-workflow-extension is an agent published in the GitHub repository sflandergan/agentic-coding (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 552 tokens. 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 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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.