Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/chrono-meta/forge-harnessnpx agentmods add skills/chrono-meta/forge-harness/install-wizardWrote 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/chrono-meta/forge-harness/install-wizard)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/install-wizard"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/install-wizard.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
- medium Excessive Agency · line 36 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.
- medium Excessive Agency · line 44 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.00075 | $0.07104 |
| Opus 5 | $0.00037 | $0.03552 |
| Sonnet 5 | $0.00015 | $0.01421 |
| Haiku 4.5 | $0.00007 | $0.00710 |
Grade A, and why
install-wizard 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 7d 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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
install-wizard — Onboarding Setup Wizard
⚠️ Prerequisite — Read first if this is your first install
This skill is available after the fh-meta plugin is registered in Claude Code. If you type
/install-wizardand CC doesn't respond, the plugin hasn't been registered yet.When running Claude Code from the FH directory: the AI detects the MISS automatically and installs the plugin via Bash — no manual input needed. Just say "install the plugin."
Manual fallback (if needed):
claude plugin marketplace add https://github.com/chrono-meta/forge-harness.git claude plugin install -s user fh-meta@forge-harnessAfter install, if
install-wizardappears in/skillslist in CC chat, you're ready. SeeREADME.md > Advanced Settings > Plugin Installfor detailed guide.
Run immediately after cloning forge-harness (FH), or when setting up a new project for the first time.
Sets up the periodic-audit notification structure: a permanent zshrc hook (fh_audit_check.zsh, runs on terminal start) plus FH's session-start mtime detection. Both surface a weekly-audit reminder when 7+ days have elapsed since the last weekly_audit — no persistent cron is used (a session-scoped scheduler cannot survive to fire on a later day).
Key Terms
| Term | Definition |
|---|---|
| sentinel | An empty file that records whether a specific event (audit complete, install complete, etc.) has occurred. Created in ~/.cc_sentinels/. |
| zshrc hook | Shell function added to ~/.zshrc. Automatically runs on terminal start and applies permanently. |
| session-start detection | FH's durable weekly-audit cadence — at session start the mtime of the latest weekly_audit_* is checked and /harvest-loop is proposed if 7+ days elapsed (see CLAUDE.md Cadence Rules). No persistent scheduler required. |
Execution Modes
| Mode | Trigger | Action |
|---|---|---|
| Normal mode (default) | /install-wizard |
Gap diagnosis → per-item approval → execution → zshrc/sentinel install (interactive) |
| Analysis mode | /install-wizard --dry-run |
Gap diagnosis + report output only. No approval gate or execution. bg dispatch compatible |
What ships with it
1 file 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.
- 7d ago First seen · 385 lines · 75 tokens per session scan A 7bbffc519896
install-wizard is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 7,104 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
taiyi-requirement
A requirements-analysis process that turns a proposed change into a REQUIREMENT.md document. It records user needs, acceptance checks, terminology, triggers, and dependencies, with different levels of detail for different project sizes.
taiyi-change
A TaiyiForge workflow stage for writing a change proposal in CHANGE.md, with checks for scope, risks, success criteria, and related project documents.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-compress
A workflow tool for shrinking large coding-agent conversations and work files into shorter context notes. It can also coordinate separate agents for parallel development and create handoff notes for continuing work in a new session.