setup

setup is a skill for Claude Code, Codex from TrentM6/baseline-core. It costs 63 tokens per session (3,362 once invoked), scanned A, original, MIT.

A guided setup process for a new Baseline System that reads existing documents, such as a pitch deck or product specification, and turns them into context files. It asks focused questions for information the documents do not provide.

In plain words
What is it for?
Use it after initializing Baseline System to establish identity, product, brand, and other working context for later skills.
Why use it?
It avoids making users repeat information they already have and reduces the risk of starting with missing or incorrect context.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the AskUserQuestion tool.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is Follow the [Workflow Orchestration Pattern](../../frameworks/workflow-orchestration.md) for the universal workflow approach. Below are the setup-specific detail.

Good fit Use it after initializing Baseline System to establish identity, product, brand, and other working context for later skills.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/TrentM6/baseline-core
agentmods
npx agentmods add skills/trentm6/baseline-core/setup

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/trentm6/baseline-core/setup/github.svg)](https://agentmods.dev/skills/trentm6/baseline-core/setup)
Your own site
<a href="https://agentmods.dev/skills/trentm6/baseline-core/setup"><img src="https://agentmods.dev/badge/skills/trentm6/baseline-core/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.

agentmods 80×15 button for setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/trentm6/baseline-core/setup"><img src="https://agentmods.dev/badge/skills/trentm6/baseline-core/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,362 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00063 $0.03362
Opus 5.5 $0.00025 $0.01345
Sonnet 5.5 $0.00013 $0.00672
Haiku 4.5 $0.00006 $0.00336

Measured yesterday against content hash eb58ee282a84, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 yesterday.

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/setup-skill.md · 258 lines

How it starts

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

Setup

Setup is how a freshly-scaffolded Baseline System learns who the user is. It runs once per system. Every other skill produces better output because of what setup captures.

The default path is doc-first: most users have written collateral already (pitch deck, one-pager, brand guide, product spec). Have them drop those in chat, parse what fits each context file, confirm with the user, write to disk. Then ask short gap-filling questions only for what the docs didn't cover. Users with no docs run a guided questionnaire instead — but with multiple-choice options where they make sense, not 80 cold open prompts.


Core Principles

  1. Use what the user already has. A pitch deck answers half the identity questions for free. Don't ask a user to retype what they can paste.

  2. Show drafts, don't just write. Before saving any context file, show the user the draft you extracted or composed and ask for confirmation. Edits are cheap when proposed; expensive when discovered later.

  3. Ask fewer, sharper questions. A multiple-choice "what stage are you?" beats an open "describe your company stage." Always offer free-text fallback.

  4. Voice is special — get a sample first. Asking "what's your voice?" cold produces useless answers. Ask for 2-3 samples of the user's existing writing and infer voice rules from them. See voice-elicitation.md.

  5. Never block on missing context. If the user can't or won't answer something, write what you have and move on. Empty context produces more generic output, not broken output.

  6. Stage-aware. A pre-launch company can't answer "what's your typical deal size." A growth-stage company doesn't need to redo positioning. Ask the user's stage first; skip questions that don't apply.

  7. One pass per file. Don't loop back to identity.md after moving to product.md. If the user wants to revise, they can re-run setup or edit the file directly.


Workflow

Follow the Workflow Orchestration Pattern for the universal workflow approach. Below are the setup-specific details for each step.

Read the full file on GitHub · 258 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. yesterday First seen · 258 lines · 63 tokens per session scan A eb58ee282a84

Subscribe to this mod's changes

setup is a skill published in the GitHub repository TrentM6/baseline-core (23 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 3,362 once invoked, about $0.0003 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-11-17.

Related

setup compared with skills from other repositories

setup next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
setupTrentM6/baseline-coreSkill232d agoMITA63Claude Code, Codex
imagegenopenai/codexSkill136ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill80kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill101ktodayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill395ktodayMITA36Claude Code
free-llm-apismnfst/awesome-free-llm-apisSkill14ktodayCC0-1.0A113Claude Code, Codex
next-cache-components-adoptionvercel/next.jsSkill144ktodayMITA95Claude Code