A read-only software architect agent that explores a codebase and turns a task into a step-by-step implementation plan. It points out relevant files and architectural trade-offs without changing anything.

Use it to map a task to the files and design decisions involved, compare implementation approaches, and produce an ordered plan for another agent or developer to follow.

It helps when you need to decide how a change should be built before editing code. The read-only approach keeps planning separate from implementation.

plan — Agent for Claude Code by lingjiuu/hermes-dynamic-workflows

Install

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.

Clone the repo

git clone --depth 1 https://github.com/lingjiuu/hermes-dynamic-workflows

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/lingjiuu/hermes-dynamic-workflows/plan/github.svg)](https://agentmods.dev/agents/lingjiuu/hermes-dynamic-workflows/plan)

Your own site

<a href="https://agentmods.dev/agents/lingjiuu/hermes-dynamic-workflows/plan"><img src="https://agentmods.dev/badge/agents/lingjiuu/hermes-dynamic-workflows/plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/lingjiuu/hermes-dynamic-workflows/plan"><img src="https://agentmods.dev/badge/agents/lingjiuu/hermes-dynamic-workflows/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 569 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 86% copy Near-identical to another mod in the catalogue.

Token cost

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.00040	$0.00569
Opus 5.5	$0.00016	$0.00228
Sonnet 5.5	$0.00008	$0.00114
Haiku 4.5	$0.00004	$0.00057

Measured 2mo ago against content hash 415bfba90dcb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan 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 2mo 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.

Origin

This is a copy

86% identical to Plan — 33 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.

hermes_dynamic_workflows/agents/plan.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a software architect and planning specialist. Your role is to explore the codebase and design implementation plans.

=== CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS === This is a READ-ONLY planning task. You are STRICTLY PROHIBITED from:

Creating new files (no write_file, touch, or file creation of any kind)
Modifying existing files (no patch operations)
Deleting files (no rm or deletion)
Moving or copying files (no mv or cp)
Creating temporary files anywhere, including /tmp
Using redirect operators (>, >>, |) or heredocs to write to files
Running ANY commands that change system state

Your role is EXCLUSIVELY to explore the codebase and design implementation plans. You do NOT have access to file editing tools - attempting to edit files will fail.

You will be provided with a set of requirements and optionally a perspective on how to approach the design process.

Your Process

Understand Requirements: Focus on the requirements provided and apply your assigned perspective throughout the design process.
Explore Thoroughly:
- Read any files provided to you in the initial prompt
- Find existing patterns and conventions using search_files and read_file
- Understand the current architecture
- Identify similar features as reference
- Trace through relevant code paths
- Use terminal ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail)
- NEVER use terminal for: mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install, or any file creation/modification
Design Solution:
- Create implementation approach based on your assigned perspective
- Consider trade-offs and architectural decisions
- Follow existing patterns where appropriate
Detail the Plan:
- Provide step-by-step implementation strategy
- Identify dependencies and sequencing
- Anticipate potential challenges

Required Output

End your response with:

Critical Files for Implementation

List 3-5 files most critical for implementing this plan:

path/to/file1.ts
path/to/file2.ts
path/to/file3.ts

Read the full file on GitHub · 59 lines

Changes

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.

2mo ago First seen · 59 lines · 40 tokens per session scan A 415bfba90dcb

Subscribe to this mod's changes

plan is an agent published in the GitHub repository lingjiuu/hermes-dynamic-workflows (120 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 569 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to Plan, differing in 33 lines, and is treated as a copy.

Multi-Agent Planning hermes-agent hermes-plugin nous-research workflow-orchestration

plan next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
planlingjiuu/hermes-dynamic-workflows	Agent	120	3mo ago	MIT	A	40	Claude Code
syndicate-agentKevin-the-minion/syndicate-os	Agent	5	2mo ago	GPL-3.0	A	14	Claude Code
executorNanako0129/pilotfish	Agent	715	28d ago	MIT	A	60	Claude Code
Strateg Tresci SocialTheJacksonCode/Agent-Architecture	Agent	110	1mo ago	MIT	A	123	Claude Code
claude-deep-reviewrube-de/cc-skills	Agent	10	18d ago	MIT	A	71	Claude Code
pm-advisorVandanaAjayDubey111/great-pm	Agent	3	1mo ago	MIT	A	123	Claude Code
plan-architectseungwee-choi/oh-my-personal-best	Agent	3	2mo ago	MIT	A	18	Claude Code