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/nikiforovall/claude-code-rules/agentic-workflowsgit clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWhat 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.00024 | $0.02030 |
| Opus 5 | $0.00012 | $0.01015 |
| Sonnet 5 | $0.00005 | $0.00406 |
| Haiku 4.5 | $0.00002 | $0.00203 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 179 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
Workflows may optionally include:
- Project tracking / monitoring (GitHub Projects updates, status reporting)
- Orchestration / coordination (one workflow assigning agents or dispatching and coordinating other workflows)
Files This Applies To
- Workflow files:
.github/workflows/*.mdand.github/workflows/**/*.md - Workflow lock files:
.github/workflows/*.lock.yml - Shared components:
.github/workflows/shared/*.md - Configuration: https://github.com/github/gh-aw/blob/v0.64.2/.github/aw/github-agentic-workflows.md
Problems This Solves
- Workflow Creation: Design secure, validated agentic workflows with proper triggers, tools, and permissions
- Workflow Debugging: Analyze logs, identify missing tools, investigate failures, and fix configuration issues
- Version Upgrades: Migrate workflows to new gh-aw versions, apply codemods, fix breaking changes
- Component Design: Create reusable shared workflow components that wrap MCP servers
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 · 179 lines · 24 tokens per session scan A 552935d28816
agentic-workflows is an agent published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 4d ago), licensed Apache-2.0. It adds 24 tokens to every session and 2,030 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
cursor-worker
Delegates one self-contained coding or research task to the Cursor CLI (cursor-agent), running it on the Cursor subscription's quota instead of Claude's. Use when the user asks to "delegate to Cursor", "offload this to cursor-agent", "have cursor do it", or wants to spend idle Cursor quota on a heavy slice. Uses the…
qg-design
Use this agent to validate Design phase output against domain-specific quality criteria. Checks architecture consistency, STRIDE security coverage, API-story mapping, design-time test specifications, ADR presence, and data model integrity. Returns PASS/WARN/FAIL verdict. Invoked automatically after design generation…
knowledge-curator
Use this agent to capture knowledge from AI-assisted development cycles. Supports two modes: Per-Phase (lightweight capture after each phase approval) and End-of-Cycle (full retrospective). Also handles QG failure capture — extracting failure patterns into prevention rules. Context: A phase has just been approved and…
design-architect
Use this agent when the user needs to create or update technical designs for approved requirements. This includes architecture design, API design, data model design, security threat modeling (STRIDE), Architecture Decision Records (ADRs), and design-time test specifications. Trigger this agent during the Design phase.…
agent-creator
Generate the instruction bundle (AGENTS.md body, SOUL.md, HEARTBEAT.md, TOOLS.md) for a single Paperclip company agent. Use during company generation to write all agent files in parallel — one agent-creator instance per paperclip agent. Context: Company generation Phase 6a — writing agent files in parallel user…
skill-creator
Create properly structured SKILL.md files for Paperclip company agents. Use during company generation to write all custom skills in parallel. Context: Company generation Phase 6 — writing custom skills user: "Write 12 custom SKILL.md files for Figurio" assistant: "I'll use the skill-creator agent to generate properly…