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-implement-level5npx skills add maksutovic/joycraft --skill joycraft-implement-level5git 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-implement-level5)<a href="https://agentmods.dev/skills/maksutovic/joycraft/joycraft-implement-level5"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/joycraft-implement-level5.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.1 | $0.00039 | $0.01731 |
| Opus 5 | $0.00019 | $0.00865 |
| Sonnet 5 | $0.00008 | $0.00346 |
| Haiku 4.5 | $0.00004 | $0.00173 |
Grade A, and why
joycraft-implement-level5 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 6d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Level 5 — Autonomous Development Loop
You are guiding the user through setting up Level 5: the autonomous feedback loop where specs go in, validated software comes out. This is a one-time setup that installs workflows, creates a scenarios repo, and configures the autofix loop.
Before You Begin
Check prerequisites:
- Project must be initialized. Look for
docs/.joycraft/state.json(older installs may still have it at the legacy.claude/.joycraft/state.jsonor a.joycraft-versionat the repo root). If none exist, tell the user to runnpx joycraft@latest initfirst. - Project should be at Level 4. Check
docs$joycraft-assessment.mdif it exists. If the project hasn't been assessed yet, suggest running$joycraft-tunefirst. But don't block — the user may know they're ready. - Git repo with GitHub remote. This setup requires GitHub Actions. Check for
.git/and a GitHub remote.
If prerequisites aren't met, explain what's needed and stop.
Step 1: Explain What Level 5 Means
Tell the user:
Level 5 is the autonomous loop. When you push specs, three things happen automatically:
- Scenario evolution — A separate AI agent reads your specs and writes holdout tests in a private scenarios repo. These tests are invisible to your coding agent.
- Autofix — When CI fails on a PR, Claude Code automatically attempts a fix (up to 3 times).
- Holdout validation — When CI passes, your scenarios repo runs behavioral tests against the PR. Results post as PR comments.
The key insight: your coding agent never sees the scenario tests. This prevents it from gaming the test suite — like a validation set in machine learning.
Step 2: Gather Configuration
Ask these questions one at a time:
Question 1: Scenarios repo name
What should we call your scenarios repo? It'll be a private repo that holds your holdout tests.
Default:
{current-repo-name}-scenarios
Accept the default or the user's choice.
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.
- 6d ago First seen · 165 lines · 39 tokens per session scan A bd719467d595
joycraft-implement-level5 is a skill published in the GitHub repository maksutovic/joycraft (15 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 1,731 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", "уроки дизайна"…
task-decomposition
Decompose approved tech-spec into atomic task files with parallel creation and validation. Use when: "разбей на задачи", "декомпозиция", "decompose tech-spec", "создай задачи из техспека", "/decompose-tech-spec".
design-generate
Generates HTML/CSS pages and static SVG mockups from text descriptions using a project's design system. Selects from 15 layout patterns (5 basic + 10 advanced grids), assembles components, applies tokens, supports iteration via screenshots. After approval, generates diagonal before/after collage. Use when: "сделай…
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: "создай дизайн-систему", "инициализируй…
feature-execution
Orchestrate feature delivery as team lead: spawn agents by wave, manage review cycles (max 3 rounds), commit per wave. Use when: "выполни фичу", "do feature", "execute feature", "запусти фичу", "выполни все задачи", "execute all tasks".