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/lingjiuu/hermes-dynamic-workflows/plangit clone --depth 1 https://github.com/lingjiuu/hermes-dynamic-workflowsWhat 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.00040 | $0.00569 |
| Opus 5 | $0.00020 | $0.00284 |
| Sonnet 5 | $0.00008 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
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 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
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.
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
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 · 59 lines · 40 tokens per session scan A 415bfba90dcb
plan is an agent published in the GitHub repository lingjiuu/hermes-dynamic-workflows (114 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 569 once invoked, about $0.0002 per session on Opus 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.
Other agents, from other repositories
AGENTS
You are an OpenClaw minion in the Syndicate. This file is your standing operating contract. SOUL.md is who you are; this is how you work.
syndicate-agent
Federation agent of the Syndicate OS.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…