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/huifer/zeus/zeus-plannergit clone --depth 1 https://github.com/huifer/zeusWrote 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/huifer/zeus/zeus-planner)<a href="https://agentmods.dev/agents/huifer/zeus/zeus-planner"><img src="https://agentmods.dev/badge/agents/huifer/zeus/zeus-planner.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.00025 | $0.00147 |
| Opus 5 | $0.00013 | $0.00073 |
| Sonnet 5 | $0.00005 | $0.00029 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
zeus-planner 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 4d 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.
What it actually says
You are the planning specialist for Zeus.
Responsibilities:
- Parse approved spec files into user stories with measurable acceptance criteria.
- Decompose stories into small executable tasks.
- Build dependency-safe waves for parallel execution.
- Ensure artifact consistency across
prd.json,task.json, androadmap.json.
Quality standards:
- No duplicate IDs.
- No orphan task without a story.
- No cyclic task dependencies.
- Priorities must align to north star impact.
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.
- 4d ago First seen · 21 lines · 25 tokens per session scan A 1f9665d6ab8f
zeus-planner is an agent published in the GitHub repository huifer/zeus (21 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 147 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
Anti-Vibe Writing Dev
Use when developing anti-vibe-writing, a writing skill for AI agents that rewrites generated drafts into a more classic, polished, human style. Handles skill design, prompt assets, editing heuristics, README cleanup, docs maintenance, and safe local git automation.
taste-judge
Final-gate taste judge running a 3-lens internal panel over what rubrics cannot capture. Use SPARINGLY on high-stakes work (signature designs, hero copy, brand directions, architecture choices, must-be-right documents), normally after a deliverable has passed two clean verifier sweeps. Also use to rank best-of-N…
star-chamber
Advisory multi-LLM craftsmanship council. Invoked for significant architectural decisions, design trade-off analysis, and multi-perspective code review of complex implementations.
memory_directory
This file records the default memory directories used by SkillFlow's built-in agent profiles. These paths match the defaults in core/agentintegration/domain/defaults.go.
drift-analyst
Use when /gc runs or the calling agent needs a fresh-context scan for code drift, entropy, or AI slop before wrapping up. Checks changed/active code against the project's golden-rules.md plus generic drift heuristics (duplicated helpers, inconsistent error handling, copy-paste blocks, oversized files, TODO pileup…
002-multi-agent-export
Export skills to any supported AI agent's directory structure (Claude, Cursor, Codex, etc.).