agentmods.dev

setup-project

A setup tool that creates instruction files for the coding assistants used by a project, such as Claude Code, Codex, Cursor, or GitHub Copilot.

In plain words
What is it for?
Use it to generate assistant-specific files such as AGENTS.md, CLAUDE.md, Cursor rules, or Copilot instructions, including optional settings for multi-phase initiatives.
Why use it?
It gives different assistants shared project guidance without requiring the team to create each configuration file by hand.

Skill for Claude CodeCodex

Part of the hotl plugin — 20 skills, 9 commands, 1 agent, 1 hook shipped together

26 1mo ago A scan 39 tokens original MIT
View the source file yimwoo/hotl-plugin
Install

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.

agentmods
npx agentmods add skills/yimwoo/hotl-plugin/setup-project
Any agent
npx skills add yimwoo/hotl-plugin --skill setup-project
Clone the repo
git clone --depth 1 https://github.com/yimwoo/hotl-plugin

Made for: Claude Code, Codex.

Or install hotl, the plugin that ships this one along with the rest of its 20 skills, 9 commands, 1 agent, 1 hook.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,606 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.01606
Opus 5 $0.00019 $0.00803
Sonnet 5 $0.00008 $0.00321
Haiku 4.5 $0.00004 $0.00161

Measured 3d ago against content hash 8ed085c18cce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-project 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.

skills/setup-project/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Setup Project for HOTL

Overview

Generate the right config files so every code assistant on your team follows HOTL principles.

Announce: "Running HOTL project setup. Let me check what tools your team uses."

Process

  1. Ask: "Which code assistants does your team use?" (select all that apply)

    • Claude Code
    • Codex (OpenAI)
    • Cline (VS Code extension)
    • Cursor
    • GitHub Copilot

  2. Ask: "Will this project run multi-phase initiatives?" Default: no. Only answer yes for multi-phase work like major migrations, v1/v2 rewrites, platform rebuilds, or any effort that will span multiple phases with separate phase design docs and workflows. For a single feature, bug fix, or refactor, answer no — the standard HOTL flow handles those just fine.

    If yes, ask the follow-up: "What's the initiative slug? (kebab-case, e.g. ai-assurance, v2-migration)". Validate the answer matches [a-z0-9][a-z0-9-]*.

    If no (or if the user declines to opt in), skip step 5 entirely and proceed with tool-adapter generation only.

  3. For each selected tool, generate the appropriate file:

Tool File Generated Location
Claude Code CLAUDE.md Project root
Codex AGENTS.md; optional .codex/agents/*.toml Project root
Cline .clinerules Project root
Cursor .cursor/rules/hotl.md Project root
GitHub Copilot .github/copilot-instructions.md Project root

  1. Each generated file contains:

    • HOTL operating principles (intent/verification/governance contracts)
    • Brainstorming guidance that produces design docs in docs/designs/
    • Link to docs/plans/YYYY-MM-DD-<slug>-workflow.md format
    • Risk level guidelines
    • What always requires human review

  2. If Codex was selected, ask whether to install HOTL Codex custom agent templates. Default: yes. These templates make the bundled reviewer, architect, researcher, QA, dev, and PM roles available to the target project as Codex project-scoped custom agents.

Read the full file on GitHub · 128 lines

Changes

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.

  1. 3d ago First seen · 128 lines · 39 tokens per session scan A 8ed085c18cce

Subscribe to this mod's changes

setup-project is a skill published in the GitHub repository yimwoo/hotl-plugin (26 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,606 once invoked, about $0.0002 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.

Building agentsagent-workflowai-codingclaude-codeclinecodexdeveloper-tools
Related

Other skills, from other repositories

first-plan-co-change-analysis

Skill que constrói o Co-change Graph - "quando arquivo X muda, qual outro arquivo geralmente muda junto?". Use durante Discovery e em /fp:cochange. Baseado em git history. Detecta arquivos co-dependentes que devem ser editados juntos para evitar PRs incompletos. v0.3.0+ usa engine nativo Rust quando disponível…

vynazevedo/first-plan · 88 tokens

first-plan-provenance-tracker

Skill que define o schema de proveniência e o sistema de freshness tracking para findings em .first-plan/. Use durante Discovery e refresh para registrar source (file:line@SHA), TTL, confidence inicial e cadeia de supersedeção. Aplica decay de confidence baseado em idade.

vynazevedo/first-plan · 64 tokens

first-plan-git-intelligence

Skill que extrai inteligência do git history - heatmap de atividade, ownership, branches/PRs in-flight. Use durante Discovery e em /fp:hot, /fp:owner, /fp:in-flight. Tudo via comandos git read-only.

vynazevedo/first-plan · 58 tokens

first-plan-protocol

Esta skill DEVE ser carregada em qualquer comando do plugin first-plan. Define o protocolo PLAN-FIRST (Discovery -> Plan -> Approval -> Execution -> Report), as 7 regras invioláveis e o comportamento esperado em cada fase. Ative quando o usuário invocar /fp: ou mencionar "first-plan", "context compilation", "discovery…

vynazevedo/first-plan · 81 tokens

first-plan-reconciliation

Skill que define Spec-Code Reconciliation - matching contínuo entre artefatos de intenção (docs, specs, JIRA, GitHub issues) e implementação (código, testes, PRs). Use durante Discovery e em /fp:check para identificar feature ja implementada, em flight, drifted ou abandonada.

vynazevedo/first-plan · 70 tokens

first-plan-semantic-reuse

Skill que faz busca semantica via BM25 sobre o indice de simbolos do projeto. Substitui grep do reuse-index quando o engine nativo esta disponivel. Encontra "preciso de validacao de email" mesmo se a funcao se chama validateEmailRFC. Use durante /fp:reuse e /fp:plan para identificar componentes reusaveis com matching…

vynazevedo/first-plan · 88 tokens