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-status/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-status)<a href="https://agentmods.dev/skills/huifer/zeus/zeus-status"><img src="https://agentmods.dev/badge/skills/huifer/zeus/zeus-status/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.
<a href="https://agentmods.dev/skills/huifer/zeus/zeus-status"><img src="https://agentmods.dev/badge/skills/huifer/zeus/zeus-status.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00449 |
| Opus 5.5 | $0.00013 | $0.00180 |
| Sonnet 5.5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
zeus-status 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 1mo 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
Zeus Status - Global Health Report
Render a deterministic snapshot across active versions and recommend the next best action.
Preconditions
.zeus/main/config.jsonexists.- All referenced version folders are readable.
Deterministic workflow
1) Load project state
Read:
.zeus/main/config.json- each active version's
config.json,prd.json,task.json,feedback/*,evolution.md - recent AI logs (up to 5)
2) Compute report metrics
For each version compute:
- story totals and pass state,
- task totals and completion percentage,
- current/next pending wave,
- recent completed task titles.
For global scope compute:
- latest feedback attributions,
- latest evolution events,
- latest AI log highlights.
3) Select next-action recommendation
Decision table:
- missing config ->
/zeus:init - codebase map exists but config not imported ->
/zeus:init --import-existing - no tasks ->
/zeus:brainstorm --full - pending tasks ->
/zeus:execute - tasks complete but no feedback ->
/zeus:feedback - evolution signal unresolved ->
/zeus:evolve - stable ->
/zeus:brainstorm --feature <next-feature>
Brownfield freshness recommendation:
- if
.zeus/{version}/codebase-map.jsonis stale relative to recent repository changes, recommend/zeus:discover --version {version}before planning.
4) Render output
Render concise or full format depending on --brief.
5) Optional health index
If metric weights and enough feedback data exist, compute weighted health score trend.
Output contract
- clear version-by-version progress,
- clear recommendation with rationale,
- no ambiguous next step.
Agent collaboration
Use zeus-docs for consistency checks on report terminology and formatting quality.
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.
- 1mo ago First seen · 75 lines · 0 tokens per session scan A 4d8ef6df16e7
zeus-status is a skill published in the GitHub repository huifer/zeus (22 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 449 once invoked, about $0.0001 per session on Opus 5.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
zero-to-prod-orchestrator
Master orchestrator to build an application from scratch to a production-ready release, enforcing strict step-by-step progression and continuous documentation / Orkestrator utama untuk membangun aplikasi dari nol hingga rilis siap produksi dengan dokumentasi bertahap.
monorepo-architect
Expert guide for designing and managing scalable monorepos using Turborepo, pnpm workspaces, and shared packages / Panduan ahli untuk merancang dan mengelola monorepo skalabel menggunakan Turborepo dan pnpm workspaces.
n8n-automation-expert
Expert guide for workflow automation (n8n, Zapier, Make), custom nodes, webhook triggers, and AI-powered automation chains / Panduan ahli otomasi workflow (n8n, Zapier, Make), custom nodes, webhook triggers, dan rantai otomasi berbasis AI.
system-brief
Capture one system — the whole assembly of capabilities — as a brief complete enough that each capability line is a one-shot input to /capability-brief and the mission, language, and decisions seed the sbce system doc without a question. Runs the stakeholder interview once, at inception, checks the result against a…
skill-register-care
Pflege-Skill, der das dreiteilige Skill-Register konsistent hält (code-skill-index-Kataloge, Skill-Index, SKILL-MAP Family-/Routing-Map). Nutze diesen Skill für einen Drift-Check zwischen dem realen Skill-Inventar und dem dokumentierten Register: fehlende oder zu viele Einträge melden, Counts korrigieren, Stand-Datum…
requirement-delivery
A workflow for turning a new software request into a small, working deliverable. It clarifies acceptance criteria, identifies boundaries, breaks work into demonstrable parts, and looks for existing code or tools to reuse.