A setup guide for installing Big Emotion’s shared project standard in a code repository, or checking whether an existing repository follows it. It covers automated checks, Git hooks, project skills, Atlassian tools, release rules, and deployment settings.

Use it to start or audit a Big Emotion project, add checks such as linting and tests, configure Jira and Confluence, set branch and release rules, and prepare deployment and secret-handling settings.

It removes the need to configure these project conventions by hand and helps identify missing pieces in an existing repository.

setup — Skill for Claude Code and Codex by big-emotion: A setup guide for installing Big Emotion’s shared project…

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/big-emotion/agent-atelier/setup

Any agent

npx skills add big-emotion/agent-atelier --skill setup

Clone the repo

git clone --depth 1 https://github.com/big-emotion/agent-atelier

Made for: Claude Code, Codex.

Or install project-standard, the plugin that ships this one along with the rest of its 1 skill.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/big-emotion/agent-atelier/setup.svg)](https://agentmods.dev/skills/big-emotion/agent-atelier/setup)

Your own site

<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/setup"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/setup.svg" alt="Measured on agentmods" height="20"></a>

Per session 125 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,932 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.

Model	Per session	Once invoked
Fable 5	$0.00125	$0.01932
Opus 5	$0.00063	$0.00966
Sonnet 5	$0.00025	$0.00386
Haiku 4.5	$0.00013	$0.00193

Measured 4d ago against content hash 50a9e9b96ecd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (templates/m2-hooks/commitlint.config.mjs, templates/m2-hooks/lint-staged.config.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/project-standard/skills/setup/SKILL.md · 83 lines

How it starts

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

Big Emotion Project Setup

Every Big Emotion project ships the same toolset. This skill installs it, module by module, on any repo — or audits an existing repo against it. The full rationale lives in SPEC.md at the root of the agent-atelier repository.

Module	What	Reference
M1	CI quality gates (gitleaks, lint, typecheck, format, test, build)	`references/m1-ci.md`
M2	Husky hooks (pre-commit → lint-staged, commit-msg → commitlint)	`references/m2-hooks.md`
M3	Project skills `<slug>-{release,audit,spec,ticket,bootstrap-confluence}`	`references/m3-skills.md`
M4	Atlassian wiring (Jira board, Confluence spec tree, config)	`references/m4-atlassian.md`
M5	Ferry (router model, claude-code path)	`references/m5-ferry.md`
M6	Branch & release model (develop/main, tag `v*` → deploy)	`references/m6-branch-release.md`
M7	Infrastructure & secrets (OVH VPS + Traefik, Azure variant, M365 mail, secrets doctrine)	`references/m7-infra.md`

Reference paths above are relative to ${CLAUDE_PLUGIN_ROOT}/skills/setup/. Templates live in ${CLAUDE_PLUGIN_ROOT}/skills/setup/templates/; the placeholder registry is templates/params.json.

Operating rules

Never write before the plan is confirmed. Steps 1–3 are read-only; a single explicit confirmation covers the whole install plan.
Idempotent. On a compliant repo, report "compliant" and change nothing. Never overwrite a project's existing customization of a module without flagging it as drift and asking.
Modules are independent. Install only what the user selected; missing prerequisites between modules (M5 needs M4's board; M3's spec skill needs M4's config) are declared in the plan, not silently added.
Everything written is in English (code, comments, docs). User-facing trigger phrases inside skills may stay French.
Adapt, don't force. Templates ship in pnpm/TypeScript form; adapt commands to the interview answers (package manager, toolchain layout, no-TS repos) per each module's reference doc.
Secret names, never values. The skill documents where every secret lives, what it is called, and how to obtain it — it never writes, echoes, or stores a secret value (not in rendered files, not in conversation output, not in this plugin). Values are entered by a human directly at their destination (GitHub secret, VPS .env, provider portal). This plugin is public and ships no infrastructure coordinates — no hostnames, IPs, SSH ports, account handles or resource names. Collect them from the user at interview time and never write them back into the plugin.

Read the full file on GitHub · 83 lines

Files

What ships with it

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

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.

4d ago First seen · 83 lines · 125 tokens per session scan A 50a9e9b96ecd

Subscribe to this mod's changes

setup is a skill published in the GitHub repository big-emotion/agent-atelier (2 stars, last pushed 1mo ago), licensed MIT. It adds 125 tokens to every session and 1,932 once invoked, about $0.0006 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.

CI and CD DevOps and cloud Git and workflow atlassian claude-code claude-code-plugin conventional-commits developer-tooling

setup-pipeline

Sets up a Power Platform Pipeline for automated Power Pages deployments. Power Platform Pipelines is Microsoft's native CI/CD tool built into the Power Platform — no external infrastructure required. Use when asked to: "set up ci/cd", "create pipeline", "setup pipeline", "set up power platform pipelines", "create…

microsoft/power-platform-skills · 118 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

add-azuredevops

Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.

microsoft/power-platform-skills · 37 tokens

pr-watch

Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.

SethGammon/Citadel · 46 tokens

push-ci

Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).

sd0xdev/sd0x-harness · 82 tokens

cloudflare-workers-ci-cd

Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.

secondsky/claude-skills · 50 tokens