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 an8079/take-skills --skill hudgit clone --depth 1 https://github.com/an8079/take-skillsWrote 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/an8079/take-skills/hud)<a href="https://agentmods.dev/skills/an8079/take-skills/hud"><img src="https://agentmods.dev/badge/skills/an8079/take-skills/hud/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/an8079/take-skills/hud"><img src="https://agentmods.dev/badge/skills/an8079/take-skills/hud.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.00000 | $0.01547 |
| Opus 5 | $0.00000 | $0.00773 |
| Sonnet 5 | $0.00000 | $0.00309 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
hud 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 9d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hud — Real-Time Task Status HUD
name
hud
description
任务实时状态 HUD(Head-Up Display):以飞行员 HUD 的方式,在每个任务执行节点实时推送状态更新。HUD 不打断工作流,而是以紧凑的可视化格式呈现进度、资源消耗、风险预警。与 progress-tracking(事后报告式)不同,hud 是主动推送式——持续显示当前状态,让用户始终知道"现在在哪"。
when to activate
用户说以下话时激活:
- "hud"
- "显示进度"
- "实时状态"
- "给我一个仪表盘"
- "显示当前任务状态"
- "autopilot"(自动与 autopilot 技能联动)
- 当执行时间预计超过 5 分钟的任务时自动触发
protocol
HUD 布局规范
标准 HUD 格式(单行/双行):
┌─────────────────────────────────────────────────────────┐
│ ⬡ [项目名] ⏱ 12:34 ████████░░░░░░░░ 58% 😐 │
│ [当前任务] ──▶ [下一步] │
│ ⚠ 风险: [如有] │
└─────────────────────────────────────────────────────────┘
ANSI 彩色 HUD(CLI):
⬡ myproject 12:34 ▓▓▓▓▓▓▓▓░░░░ 58% ⏳ build:✓ test:▓▓
→ Writing index.ts ──▶ Running tests
⚠ slow query detected (>2s)
纯文本 HUD(无 ANSI):
[========----] 58% | myproject | 12:34 | BUILD:OK | TEST:RUN
-> Writing index.ts -> Running tests
[!] slow query detected (>2s)
HUD 数据源
HUD 自动读取以下数据:
| 数据字段 | 来源 | 更新频率 |
|---|---|---|
| 项目名 | 当前工作目录名 | 静态 |
| 耗时 | 计时器 | 每节点 |
| 进度条 | 已完成任务/总任务 | 每节点 |
| 当前节点 | 当前执行步骤名 | 每节点 |
| 下一步 | 队列中下一个任务 | 每节点 |
| 风险预警 | 执行过程中检测 | 实时 |
| 情绪指标 | 错误率/成功率 | 每节点 |
HUD 更新协议
更新触发点:
- 任务节点开始 → 显示节点名 + 开始时间
- 任务节点完成 → 更新进度 + 显示耗时
- 检测到风险 → 在 HUD 底部追加警告行
- 任务队列变化(添加/删除)→ 重绘进度条
- 每 30 秒(无其他事件)→ 发送心跳更新
风险等级与颜色:
- 🟡 WARNING(黄):可能延迟,但不阻塞
- 🟠 ALERT(橙):需要关注,可能影响进度
- 🔴 CRITICAL(红):阻塞性问题,需要人工介入
超时规则:
- 单节点预估时间超过 5 分钟时,显示 ⏳ 并预估剩余时间
- 单节点实际时间超过预估 2 倍时,触发 ALERT
- 连续 3 个节点超时,升级为 CRITICAL 并暂停,等待用户确认
HUD 格式化 API
提供以下 HUD 格式化函数(可在任何执行上下文中调用):
hud_start(project_name, total_steps):
┌────────────────────────────────────────┐
│ ⬡ [project_name] ⏱ 00:00 │
│ [====--------] 0/[total_steps] │
│ → 初始化... │
└────────────────────────────────────────┘
hud_update(current_step, next_step, progress_pct, elapsed):
┌────────────────────────────────────────┐
│ ⬡ [project_name] ⏱ [elapsed] │
│ [██████--------] 60% [X/Y] │
│ ✓ [完成步骤] │
│ → [当前步骤] ──▶ [下一步] │
└────────────────────────────────────────┘
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.
- 9d ago First seen · 161 lines · 0 tokens per session scan A 4bb4084f3a2d
hud is a skill published in the GitHub repository an8079/take-skills (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,547 tokens. 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…