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 skills add dongdong306/hailux --skill default_helpgit clone --depth 1 https://github.com/dongdong306/hailuxWrote 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/dongdong306/hailux/default_help)<a href="https://agentmods.dev/skills/dongdong306/hailux/default_help"><img src="https://agentmods.dev/badge/skills/dongdong306/hailux/default_help/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/dongdong306/hailux/default_help"><img src="https://agentmods.dev/badge/skills/dongdong306/hailux/default_help.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.00039 | $0.03648 |
| Opus 5 | $0.00019 | $0.01824 |
| Sonnet 5 | $0.00008 | $0.00730 |
| Haiku 4.5 | $0.00004 | $0.00365 |
Grade A, and why
help 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 2d 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hailux User Guide
hailux is a terminal AI coding assistant that supports streaming conversations, tool calls, Skills, custom commands, MCP server integration, and subagent delegation.
Command Line Interface
| Command | Description |
|---|---|
hailux |
Launch the interactive TUI |
hailux --path <dir> |
Set the working directory |
hailux --rebuild-db |
Rebuild the database (clears all history), used when migration fails; the old database is backed up first |
hailux --yolo |
YOLO mode: skip all permission confirmations (works in both TUI and non-interactive mode) |
hailux run <message> |
Non-interactive mode: send a single message and print the reply (reads from stdin if the message is omitted) |
hailux run --model <provider/model> |
Override the model specified in config |
hailux run --no-tools |
Disable all tool calls (including MCP), pure chat mode |
Permissions
By default, operations inside the working directory are allowed without confirmation:
- bash commands,
read/edit/write/grep/globinside the working directory run freely - reading sensitive files such as
.env/.env.localasks for confirmation (.env.exampleis allowed) - any operation touching content outside the working directory (e.g.
cat ../secrets.txt,rm /tmp/x, editing a file outside the project) asks for confirmation - MCP tools always ask for confirmation
Override the defaults with rules in ~/.hailux/config.toml:
[permission.bash]
"rm *" = "deny"
"git push *" = "ask"
[permission.read]
"*.env" = "allow" # 关闭 .env 读取确认
[permission.external_directory]
"C:\\Users\\me\\shared\\*" = "allow"
Choosing "always" in the permission dialog persists the rule for the current session; hailux --yolo skips all confirmations.
Slash Commands
Trigger them by starting with / in the input box. After typing /, a command completion list pops up automatically. Use ↑↓ to select, Tab or Enter to confirm:
| Command | Description |
|---|---|
/sessions |
Open session selector, switch between historical sessions |
/new |
Create a new session |
/models |
Switch models or add a new provider |
/skills |
View currently loaded skills |
/mcp |
View MCP server connection status |
/plan |
Toggle planning mode (read-only, write operations disabled) |
/exit |
Exit the program (also /quit, /q) |
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.
- 2d ago First seen · 400 lines · 39 tokens per session scan A 2766e8271798
help is a skill published in the GitHub repository dongdong306/hailux (5 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 3,648 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-09-08.
Other skills, from other repositories
gws-classroom
Google Classroom: Manage classes, rosters, and coursework.
get-rep-call-feedback
Use when the user wants evidence-backed coaching for one rep's calls, especially by comparing the rep with peer examples to identify repeatable best practices, specific upgrade moments, and practical next-call language.
recipe-create-classroom-course
Create a Google Classroom course and invite students.
tutorial
Interactive tutorial teaching Ouroboros hands-on.
printing-press-retro
Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for…
ast-grep
Use for ast-grep project setup, rule authoring, rule debugging, and structural search workflows.