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/chanmeng666/femtech-radar/agentic-workflowsgit clone --depth 1 https://github.com/ChanMeng666/femtech-radarWrote 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/agents/chanmeng666/femtech-radar/agentic-workflows)<a href="https://agentmods.dev/agents/chanmeng666/femtech-radar/agentic-workflows"><img src="https://agentmods.dev/badge/agents/chanmeng666/femtech-radar/agentic-workflows.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 | $0.00030 | $0.02792 |
| Opus 5 | $0.00015 | $0.01396 |
| Sonnet 5 | $0.00006 | $0.00558 |
| Haiku 4.5 | $0.00003 | $0.00279 |
Grade A, and why
Agentic Workflows 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 3d 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.
This is a copy
97% identical to Agentic Workflows — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Agentic Workflows Agent
This agent helps you work with GitHub Agentic Workflows (gh-aw), a CLI extension for creating AI-powered workflows in natural language using markdown files.
What This Agent Does
This is a dispatcher agent that routes your request to the appropriate specialized prompt based on your task:
- Creating new workflows: Routes to
createprompt - Updating existing workflows: Routes to
updateprompt - Debugging workflows: Routes to
debugprompt - Upgrading workflows: Routes to
upgrade-agentic-workflowsprompt - Creating report-generating workflows: Routes to
reportprompt — consult this whenever the workflow posts status updates, audits, analyses, or any structured output as issues, discussions, or comments - Creating shared components: Routes to
create-shared-agentic-workflowprompt - Fixing Dependabot PRs: Routes to
dependabotprompt — use this when Dependabot opens PRs that modify generated manifest files (.github/workflows/package.json,.github/workflows/requirements.txt,.github/workflows/go.mod). Never merge those PRs directly; instead update the source.mdfiles and rerungh aw compile --dependabotto bundle all fixes - Analyzing test coverage: Routes to
test-coverageprompt — consult this whenever the workflow reads, analyzes, or reports on test coverage data from PRs or CI runs - Rendering ASCII charts in markdown: Routes to
asciichartsguide — consult this whenever the workflow needs compact charts that render reliably in GitHub issues, comments, or discussions - CLI commands and triggering workflows: Routes to
cli-commandsguide — consult this whenever the user asks how to run, compile, debug, or manage workflows from the command line, or when they need the MCP tool equivalent of agh awcommand - Reducing token consumption / cost optimization: Routes to
token-optimizationguide — consult this whenever the user asks how to reduce token usage, lower costs, speed up workflows, or measure the impact of prompt changes with experiments - Choosing workflow architectures and design patterns: Routes to
patternsguide — consult this whenever the user asks for strategy, architecture, operating models, or pattern selection for agentic workflows
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.
- 3d ago First seen · 227 lines · 30 tokens per session scan A 4f95bc84ac9f
Agentic Workflows is an agent published in the GitHub repository ChanMeng666/femtech-radar (0 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 2,792 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to Agentic Workflows, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
use-with-codex
This page is the compatibility guide for Codex plugin and skill installation. For the normative agent protocol, use codex.md and protocol.md. The canonical Codex control command is.
any-coding-agent
Compact control guide for coding agents without a named integration — Cline, Windsurf, Devin, Aider, OpenHands, or anything else that can run a shell command or speak MCP. The named guides (codex.md, claude-code.md, cursor.md) add harness-specific hooks and skills; everything below works with none of that installed.
code-reviewer
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
karimo-investigator
Scans codebases for patterns, affected files, and architectural context. Supports three modes: task-scan (PRD interview), context-scan (first run auto-detection), and drift-check (subsequent runs).
karimo-review-architect
Code-level integration and merge quality agent — validates task PRs, resolves merge conflicts, performs feature reconciliation. Use when PM Agent needs integration validation or conflict resolution.