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 skills/huifer/zeus/zeus-feedbacknpx skills add huifer/zeus --skill zeus-feedbackgit 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-feedback)<a href="https://agentmods.dev/skills/huifer/zeus/zeus-feedback"><img src="https://agentmods.dev/badge/skills/huifer/zeus/zeus-feedback.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.00047 | $0.00609 |
| Opus 5 | $0.00023 | $0.00304 |
| Sonnet 5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
zeus-feedback 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 6d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zeus Feedback - Attribution and Evolution Trigger
Use this skill to convert real-world feedback into traceable product decisions.
Core rule
Never recommend roadmap actions before attribution analysis is complete.
Preconditions
.zeus/{version}/task.jsonexists..zeus/{version}/feedback/is writable..zeus/{version}/evolution.mdis writable.
Deterministic workflow
1) Capture raw feedback
Accept natural language, structured metrics, or mixed input.
2) Fill missing context
If essential details are missing, ask one question at a time:
- time window,
- observed metric deltas,
- user segment affected.
3) Optional metrics enrichment
If .zeus/scripts/collect-metrics.sh exists, ask for permission and run:
bash .zeus/scripts/collect-metrics.sh
Merge output into feedback evidence.
4) Run attribution analysis
Read:
- completed tasks in
.zeus/{version}/task.json - recent
.zeus/{version}/ai-logs/* - previous feedback history
- recent git commits (
git log --oneline -20)
Compute candidate task attribution with confidence score:
- high >= 0.80
- medium 0.50-0.79
- low < 0.50
5) Evaluate evolution signal
Set requires_new_version true when:
- gap is structural (not a normal iteration),
- repeated unmet need appears across feedback cycles,
- target segment diverges from current version strategy.
6) Write feedback artifact
Create .zeus/{version}/feedback/{YYYY-MM-DD-HHmmss}.json including:
- raw data,
- attribution list,
- evolution signal,
- roadmap absorption flag.
7) Append evolution timeline
Append a FEEDBACK record in .zeus/{version}/evolution.md.
8) Write AI log
Create .zeus/{version}/ai-logs/{ISO-ts}-feedback.md.
9) Ask for decision
If evolution signal is true, offer:
- A) start
/zeus:evolve - B) backlog in current roadmap
- C) ignore suggestion
10) Apply selected action
- A: invoke evolve with gap context
- B: append roadmap backlog item
- C: record-only outcome
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.
- 6d ago First seen · 110 lines · 47 tokens per session scan A 5c4b4aee1aa9
zeus-feedback is a skill published in the GitHub repository huifer/zeus (22 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 609 once invoked, about $0.0002 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…