Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add HiAgencia/hi-claude/plugin install hi-claudeWrote 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/hiagencia/hi-claude/setup)<a href="https://agentmods.dev/skills/hiagencia/hi-claude/setup"><img src="https://agentmods.dev/badge/skills/hiagencia/hi-claude/setup/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/hiagencia/hi-claude/setup"><img src="https://agentmods.dev/badge/skills/hiagencia/hi-claude/setup.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.00090 | $0.01824 |
| Opus 5 | $0.00045 | $0.00912 |
| Sonnet 5 | $0.00018 | $0.00365 |
| Haiku 4.5 | $0.00009 | $0.00182 |
Grade A, and why
setup 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hi-claude Setup
Onboard a project into the hi-claude method in ~5 minutes, interviewing the user in plain language (they may be non-technical) and generating everything from templates.
Phase 1 — Detect (no questions)
- Inspect the working directory: empty folder or existing project? Is there a
CLAUDE.md(root or.claude/)? Adocs/folder? A git repo? - Note which MCP servers, plugins, and skills are available in THIS session (they are in your context) — you will propose which ones belong in the project's CLAUDE.md.
- Detect the user's language from the conversation; generate everything in that language (templates
exist in
esanden).
Phase 2 — Interview
One AskUserQuestion call. The tool takes 2-4 closed options per question and adds "Other" for free
text, so open answers arrive through it. Ask in the user's language, with plain words.
What must be resolved by the end of the interview — the wording is yours:
| Must be resolved | Becomes |
|---|---|
| What this project is | the CLAUDE.md header, in the user's own words |
| What kind of work it is | the folder tree: src/+tests/ for code, BRAND/+content/ for marketing, research/ for documents |
| Which of the tools connected in THIS session belong to the project | the tools table, one "when to use it here" line each |
| Which limits are non-negotiable here | the LIMITING rules |
| What makes a session CLOSED, in a way that can be RUN | {{SESSION_DONE_CRITERION}} in the ROADMAP's §0 |
Ground every option in what you detected in the folder: a guess the user can correct beats a blank. For the last one, a runnable criterion is the point — the test suite green and the linter clean for code, the file published and reachable for content, every claim with its source for research.
Phase 3 — Propose (nothing written yet)
Present the exact plan: the file tree to create and the full CLAUDE.md content, built from
${CLAUDE_PLUGIN_ROOT}/skills/setup/templates/<lang>/CLAUDE.template.md with every {{PLACEHOLDER}}
filled:
What ships with it
10 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.
- templates/en/CLAUDE.template.md 3.6 KB
- templates/en/INDEX.template.md 1.5 KB
- templates/en/INVENTORY.template.md 1.4 KB
- templates/en/ROADMAP.template.md 2.0 KB
- templates/en/STATE.template.md 698 B
- templates/es/CLAUDE.template.md 3.7 KB
- templates/es/ESTADO.template.md 727 B
- templates/es/INDEX.template.md 1.5 KB
- templates/es/INVENTORY.template.md 1.4 KB
- templates/es/ROADMAP.template.md 2.0 KB
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 · 134 lines · 90 tokens per session scan A 326f58b40d4d
setup is a skill published in the GitHub repository HiAgencia/hi-claude (2 stars, last pushed 19d ago), licensed MIT. It adds 90 tokens to every session and 1,824 once invoked, about $0.0005 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.