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 agentmods add skills/maksutovic/joycraft/joycraft-collaborative-setupnpx skills add maksutovic/joycraft --skill joycraft-collaborative-setupgit clone --depth 1 https://github.com/maksutovic/joycraftWrote 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/maksutovic/joycraft/joycraft-collaborative-setup)<a href="https://agentmods.dev/skills/maksutovic/joycraft/joycraft-collaborative-setup"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/joycraft-collaborative-setup.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.01689 |
| Opus 5 | $0.00023 | $0.00844 |
| Sonnet 5 | $0.00009 | $0.00338 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
joycraft-collaborative-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 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collaborative Setup
You are setting up Joycraft for a team. Solo defaults stay solo; this skill adds the team-only ceremony — docs/areas/ folders, area README/boundaries, and a thin team-facing CONTRIBUTING-joycraft doc.
This skill is interactive — ask the user, don't auto-detect.
When to run
Run once when a team is adopting Joycraft on a multi-dev project. Solo users do not need this skill — solo defaults are fine without it.
Step 1: Confirm Team Context
Ask the user:
"Setting up Joycraft for a team? (vs. solo work) If you're unsure, you can skip — solo defaults work fine and you can run this later."
If the user says "actually solo," bail before any writes:
"No problem. The solo workflow needs no extra setup. Run
$joycraft-new-featurewhen you want to start a feature."
Step 2: Check for Flat Layout — Bail if Present
Before scaffolding team structure, check the project's docs/ for per-feature artifacts. Look for any of:
docs/features/<slug>/brief.mddocs/features/<slug>/research.mddocs/features/<slug>/design.md- Loose spec subdirectories that predate the per-feature layout (specs not under
docs/features/<slug>/specs/ordocs/bugfixes/<area>/)
If any flat layout artifacts exist, tell the user:
"I see flat-layout artifacts in your docs/ (briefs/research/designs). Run
npx joycraft@latest upgradefirst — it will migrate them intodocs/features/<slug>/automatically. Then re-run this skill."
Then stop. Skills don't reliably shell out, so the CLI does the migration.
Step 3: Gather Areas + Owners (Interactive)
Ask the user:
"How many areas does your team work in? (e.g.,
auth,api,frontend,infra) — pick names that match how your team thinks about ownership. You can also skip and just create the team CONTRIBUTING doc."
For each area name the user provides:
- Confirm the name (kebab-case).
- Ask: "Who owns this area? (a name, an email, or a team handle — used in the area README's frontmatter)"
- Ask (optional): "Are there NEVER or ASK FIRST rules specific to this area? If yes, list them; if no, skip."
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 · 167 lines · 45 tokens per session scan A af5f665b5371
joycraft-collaborative-setup is a skill published in the GitHub repository maksutovic/joycraft (15 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,689 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.
Other skills, from other repositories
code-writing
Universal quality coding process: plan, TDD, reviews. Use whenever code needs to be written — ad-hoc or as part of a task. Use when: "напиши код", "закодь", "реализуй", "write code", "implement" For planning tasks → tech-spec-planning skill. For specs → user-spec-planning skill.
design-retrospective
Analyze design session feedback, extract aesthetic lessons into .design-system/lessons-learned.md, promote recurring patterns to design-principles.md, write taste-profile and cross-project experience, generate context-free next-session prompt. Use when: "дизайн ретроспектива", "design retrospective", "уроки дизайна"…
design-system-init
Creates a project design system through scan and interview. Generates .design-system/tokens.json + standalone HTML components with CSS custom properties. Covers palette (by mood), typography (font pairs), spacing (golden ratio/Fibonacci), radii, shadows, breakpoints. Use when: "создай дизайн-систему", "инициализируй…
task-decomposition
Decompose approved tech-spec into atomic task files with parallel creation and validation. Use when: "разбей на задачи", "декомпозиция", "decompose tech-spec", "создай задачи из техспека", "/decompose-tech-spec".
tech-spec-planning
Creates tech-spec.md with architecture, decisions, testing strategy, and implementation plan. Use when: "сделай техспек", "составь техспек", "техническая спецификация", "tech spec", "создай тз", "составь тз", "new-tech-spec", "/new-tech-spec" Requires existing user-spec.md as input (create with user-spec-planning…
user-spec-planning
Creates user-spec.md through adaptive interview with codebase scanning and dual validation. Use when: "сделай юзер спек", "проведи интервью для юзер спека", "создай юзерспек", "user spec", "detailed planning", "хочу продумать фичу", "опиши требования к фиче", "сделай описание фичи", "/new-user-spec" For tech planning…