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 hujianbest/harness-flow --skill hf-to-architecturegit clone --depth 1 https://github.com/hujianbest/harness-flowWrote 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/hujianbest/harness-flow/hf-to-architecture)<a href="https://agentmods.dev/skills/hujianbest/harness-flow/hf-to-architecture"><img src="https://agentmods.dev/badge/skills/hujianbest/harness-flow/hf-to-architecture/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/hujianbest/harness-flow/hf-to-architecture"><img src="https://agentmods.dev/badge/skills/hujianbest/harness-flow/hf-to-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 23 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00078 | $0.00768 |
| Opus 5 | $0.00039 | $0.00384 |
| Sonnet 5 | $0.00016 | $0.00154 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade A, and why
hf-to-architecture 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 12d 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
hf-to-architecture
在 spec.md 已通过 hf-review(规格)之后、拆票之前,把「本片怎么建」钉成一页增量架构,供 hf-to-tickets 切垂直切片。
前置
- 冷读
spec.md、product/architecture.md（若有）、CONTEXT.md(若有)、相关 ADR,以及product/假设台账。更新progress.md为to-architecture。 - 加载
hf-codebase-design。本阶段产出仍落在本特性目录。
流程
- 对齐产品架构：写明本片落在哪些产品模块/场景上；越界须显式标注并记 ADR/假设台账，必要时回写
product/architecture.md。 - 定模块与缝:只写本特性新增或触及的模块(宜少)、各自职责、公共接口/缝;优先复用既有缝,新缝取最高可测点。用深模块词汇(小接口、大行为)。禁止复述产品架构全文。
- 关键流程与数据:画 1~3 条端到端路径;核心实体与关系几行即可,字段级细节留给票。
- 横切约定:仅写本片相对产品横切的偏离；目录与命名默认继承开发视图。
- ADR：难以逆转的决策写入
docs/adr/（或追加到product/decisions.md），正文只链接过去。 - 落盘
features/<id>/architecture.md(≤80 行),含对齐声明与机器可读确认行占位。 - 送审:按
hf-review走架构评审 →reviews/architecture-review.md。interactive等确认;auto可在非降级评审后auto-approved。 - 更新
progress.md中的当前阶段与下一步。
architecture.md 最小结构
# 架构 — <特性名>
- 日期:
- 对应规格: `spec.md`
- 用户确认:
## 对齐产品架构
<!-- 必须引用 product/architecture.md；说明落点模块/场景；越界显式写出 -->
## 本片模块与缝
## 核心数据
## 关键流程
## 横切偏离
## ADR 链接
红线
- 无
spec-review通过记录，不得写入「已确认」架构并推进到to-tickets阶段 - 存在
product/architecture.md时，正文应含对齐声明（由技能与hf-review约束） - 不在本阶段实现代码或拆完整票单(拆票是
hf-to-tickets) - 不静默填补欠定:默认选择进
product/assumptions.md
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.
- 12d ago First seen · 51 lines · 78 tokens per session scan A dc01b2408559
hf-to-architecture is a skill published in the GitHub repository hujianbest/harness-flow (53 stars, last pushed 12d ago), licensed MIT. It adds 78 tokens to every session and 768 once invoked, about $0.0004 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…