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.
npx skills add cenconq25/claude-code-app-studio --skill onboardgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/onboard)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/onboard"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/onboard/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/cenconq25/claude-code-app-studio/onboard"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/onboard.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.00065 | $0.02010 |
| Opus 5 | $0.00032 | $0.01005 |
| Sonnet 5 | $0.00013 | $0.00402 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
onboard 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 5d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributor Onboarding
Produces a single onboarding document tailored to the role. The doc is meant to be read once on day one and revisited a few times in week one — it is not a manual replacement for the codebase.
Output: production/onboarding/[role]-[date].md
Purpose / When to Run
Run when:
- A new contributor is joining the project
- An existing contributor is moving from one role to another (e.g., backend → mobile)
- The user wants a "what would I tell someone new about this project" snapshot
Do not run when no concept doc exists — onboarding without context is a tour of an empty room. Direct the user to /start first.
Inputs
- Role argument (required)
- Optional
--name <person>for personalization - All design, architecture, production artifacts on disk
Outputs
production/onboarding/[role]-[YYYY-MM-DD].md
Phase 1: Resolve Role
If no role argument was passed, ask:
- Prompt: "Which role is the onboarding for?"
- Options:
Engineer (mobile)— implements stories, writes testsDesigner (UX/visual)— authors UX specs and the design biblePM / producer— owns sprint plans, scope, milestonesQA / tester— runs test plans, files bugs, gates releasesData scientist / analytics— instrumentation, metricsOther— describe in free text
Capture the role as a kebab-case slug for the filename (engineer, designer, pm, qa, analytics, or whatever the user gives).
If --name <person> is included, the doc personalizes the welcome.
Phase 2: Gather Project Context
Read what exists. If a file is missing, note it as "not yet authored" — never invent content.
Always read:
design/concept.md.claude/docs/technical-preferences.mddesign/systems-index.md(if present)production/session-state/active.md(if present)
Role-specific reads:
| Role | Additional reads |
|---|---|
| Engineer | docs/architecture/architecture.md, docs/architecture/control-manifest.md, all Accepted ADRs, current sprint plan, docs/framework-reference/<framework>/VERSION.md |
| Designer | design/design-bible.md, all design/prd/*.md, all design/ux/*.md, the visual reference apps named in concept.md |
| PM | All sprint plans, all milestone docs, production/session-state/active.md, last 3 retrospectives |
| QA | All production/qa/ artifacts, current test plans, story types breakdown for the sprint |
| Analytics | concept.md Primary Metric, any analytics PRD, instrumentation ADRs |
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.
- 5d ago First seen · 199 lines · 65 tokens per session scan A bf49ce172358
onboard is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 2,010 once invoked, about $0.0003 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-09-03.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.