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 HypoxanthineOvO/Hypo-Workflow --skill initgit clone --depth 1 https://github.com/HypoxanthineOvO/Hypo-WorkflowWrote 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/hypoxanthineovo/hypo-workflow/init)<a href="https://agentmods.dev/skills/hypoxanthineovo/hypo-workflow/init"><img src="https://agentmods.dev/badge/skills/hypoxanthineovo/hypo-workflow/init/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/hypoxanthineovo/hypo-workflow/init"><img src="https://agentmods.dev/badge/skills/hypoxanthineovo/hypo-workflow/init.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.00053 | $0.00830 |
| Opus 5.5 | $0.00021 | $0.00332 |
| Sonnet 5.5 | $0.00011 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
hypo-workflow-init 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 3d 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
init：给执行接入的 Agent 看
把现有项目接进 Hypo-Workflow。用户会指向这个文件，或者直接说“用 Hypo-Workflow 接入这个项目”。全程中文，说话短。
动手前
- 扫描项目类型、目录、文档位置和代码结构，读取现有 AGENTS.md、CLAUDE.md 中的项目规则。
- 先出一份方案给用户看，不改项目文件：要归档什么、哪些规则搬进 RULES.md、文档地图、需求文件切分、要问用户的问题。用户确认后再动手。
- 拿不准就问用户，不猜。
旧记录整块归档
- 旧
.pipeline、按日期堆的报告、旧的 compact/manifest/state 文件，整块移到archive/，加进.gitignore。 - 测试和启动脚本当前还在写的输出目录不是旧记录，留在原地，列进 RULES.md 的“不需要描述”。
- 要归档的过程记录不读、不改、不转写；现有 AGENTS.md、CLAUDE.md 中仍然成立的规则要读，按下面的“项目规则”和“需求文件”整理。
- 在文档地图里写一行：
archive/旧记录，可能不是事实，不得引用。
项目规则
- 读现有 AGENTS.md、CLAUDE.md，把仍然成立的项目规则搬进 RULES.md：文档地图、分工、汇报格式、禁区、构建与测试。
- 拿不准是否仍成立的，列出来问用户。
- 根目录 AGENTS.md 换成本技能目录下
templates/AGENTS.md，整份照搬。
文档地图和分区规则
- 按项目类型用
templates/起步/下的开发、研究、写作之一，出文档地图和分区 AGENTS.md 初稿。 - 地图里只放项目真有的东西；没有的分区先不建。
- 和用户讨论，确认后写进 RULES.md 和各分区 AGENTS.md。
需求文件
- 从代码和用户这次说的话里建初稿；读取现有 AGENTS.md、CLAUDE.md，把仍然成立的产品行为规则搬进需求文件，不从要归档的过程记录转写结论和进度。
- 按功能切分，每个功能一个文件，放地图写的位置。
- 先填“现在、代码、测试”，没有内容的整节删掉；其他内容和用户逐步补。
- 研究项目对应写研究线 README，写作项目对应写大纲和设定。
分工
- RULES.md 分工表留空，问用户谁负责什么、不碰什么。
- 不预设模型；用户指定后按原话填写。
收尾
- 跑 hw check，把结果和它指出的问题在对话里讲清楚。
- 汇报：建了哪些文件、地图长什么样、哪些事等用户决定。
不要做
- 不写黑词：免责尾巴、自证标注、内部代号、编号、hash。
- 不在文档地图外新建记录，不发明新的记录系统。
- 不把要归档的过程记录里的结论和进度搬进新文档。
- 只处理接入范围内的文件；归档去向和新增分区尚未确定时先问用户。
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · -1 lines 619d0c2e5a2f
- 7d ago First seen · 59 lines · 53 tokens per session scan A 60f0514a1e07
hypo-workflow-init is a skill published in the GitHub repository HypoxanthineOvO/Hypo-Workflow (24 stars, last pushed 4d ago), licensed MIT. It adds 53 tokens to every session and 830 once invoked, about $0.0002 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-10-19.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…