Borrowing it
Nothing to install: this file belongs to huifer/zeus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/huifer/zeus/main/.claude/skills/zeus-plan/SKILL.mdgit 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/skills/huifer/zeus/zeus-plan)<a href="https://agentmods.dev/skills/huifer/zeus/zeus-plan"><img src="https://agentmods.dev/badge/skills/huifer/zeus/zeus-plan.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.1 | $0.00051 | $0.01071 |
| Opus 5 | $0.00026 | $0.00535 |
| Sonnet 5 | $0.00010 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
zeus-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 7d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zeus Plan - Spec to Executable Artifacts
Convert an approved spec into version-scoped stories and tasks with deterministic IDs and dependency waves.
Preconditions
- Target spec exists and is approved.
.zeus/{version}/config.jsonexists..zeus/{version}/prd.json,task.json, androadmap.jsonare writable.
Inputs
--spec <filename>(optional, default latest spec)--version vN(optional, defaultmain)
Deterministic workflow
1) Load context and reserve IDs
Read:
- selected spec
- version config
- existing
prd.json - existing
task.json
Reserve next IDs:
US-{NNN}fromprd.jsonT-{NNN}fromtask.jsonM-{NNN}fromroadmap.jsonmilestones
2) Create user stories
Extract from acceptance criteria and role/goal language in spec.
Required story shape:
{
"id": "US-001",
"title": "One-line story title",
"description": "As a <role>, I need <capability> so that <outcome>",
"acceptance_criteria": ["Given/When/Then style criterion"],
"priority": "high",
"version_scope": "main",
"passes": false,
"created_from_spec": "2026-04-07-auth-design.md",
"created_at": "2026-04-07T00:00:00.000Z"
}
Priority policy:
- high: direct north star impact
- medium: critical support path
- low: optimization or edge behavior
3) Create executable tasks
Generate small, independently executable units.
Task types:
infraapifrontenddocs
Task schema:
{
"id": "T-001",
"story_id": "US-001",
"type": "api",
"title": "Implement POST /api/auth/login",
"description": "Include validation, error mapping, and audit logging.",
"files": ["src/app/api/auth/login/route.ts"],
"depends_on": [],
"refactor_of": null,
"depends_on_existing": [],
"passes": false,
"commit_sha": null,
"ai_log_ref": null,
"wave": null,
"created_at": "2026-04-07T00:00:00.000Z"
}
Brownfield policy:
- If task modifies existing modules, fill
refactor_ofwith a stable module path or identifier. - If task depends on existing code not represented by Zeus task IDs, list those in
depends_on_existing. - Keep both fields optional for backward compatibility.
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.
- 7d ago First seen · 172 lines · 0 tokens per session scan A 85b819c38baf
zeus-plan is a skill published in the GitHub repository huifer/zeus (22 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 1,071 once invoked, about $0.0003 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 skills, from other repositories
web-static
Build modern static websites using semantic HTML and CSS without external dependencies or build systems. Also owns the verification loop for such sites — drives the rendered pages through Chrome DevTools MCP (console, accessibility snapshot, viewport resize, dark/reduced-motion emulation, Lighthouse), executes the…
web-performance-reviewer
Review web frontends for performance issues by driving the rendered site through Chrome DevTools MCP — throttled performance traces, Core Web Vitals judged against thresholds, network waterfall analysis, and heap-snapshot leak checks for SPAs. Composes on top of web-static, web-sprinkles, or web-components. Strictly…
zcfg
Integrate zcfg (Zero Dependency Configuration Utility) into Java applications. Use when adding configuration loading, reading properties files, setting up application configuration, or integrating zcfg into a Java project. Triggers on "zcfg", "add configuration", "load properties", "application configuration with…
zcl
Add colored terminal output to Java applications using zcl (Zero-dependency Colour Logger). Use when adding colored console output, terminal logging with colors, ANSI color support, or integrating zcl into a Java project. Triggers on "zcl", "colored output", "colored logging", "terminal colors", "ANSI colors"…
zargs
Add zero-dependency argument parsing to Java CLI applications using the zargs pattern — an enum-based argument parser. Use when adding CLI argument parsing, command-line option handling, or adding options to a Java project. Triggers on "zargs", "argument parsing", "CLI arguments", "command-line options", "parse…
zunit
Generate and run zunit tests for java-cli-app projects. Use when asked to create tests, write tests, add tests, or generate test files for a java-cli-app project. Triggers on "zunit", "write tests", "create tests", "add tests", "test this", "generate tests", or requests to test a java-cli-app application. Also trigger…