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-implementnpx skills add maksutovic/joycraft --skill joycraft-implementgit 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)<a href="https://agentmods.dev/skills/maksutovic/joycraft/joycraft-implement"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/joycraft-implement.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.00029 | $0.02400 |
| Opus 5 | $0.00015 | $0.01200 |
| Sonnet 5 | $0.00006 | $0.00480 |
| Haiku 4.5 | $0.00003 | $0.00240 |
Grade A, and why
joycraft-implement 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.
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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Atomic Spec
You have exactly one atomic spec file to execute. Your job is to implement it using strict TDD — tests first, confirm they fail, then implement until green.
Step 1: Parse Arguments
The user MUST provide a path. No path = stop immediately.
If no path was provided:
No spec path provided. Provide a spec file or a feature directory:
$joycraft-implement docs/features/<slug>/specs/spec-name.mdor$joycraft-implement docs/features/<slug>/
If the path is a directory (ends with / or does not end with .md):
Look for specs/.joycraft-spec-queue.json inside that directory. Read it. Find the first todo spec whose dependencies are satisfied (a dependency is satisfied once it is in-review or done). This matches what joycraft-next-spec serves. That single spec file is your target. Do NOT read any other specs.
Using spec queue: found [spec-file-name] as the next spec.
If the directory has no queue or no todo specs:
No remaining specs found in [directory].
If the path is a file ending in .md:
Use it directly as the spec to implement.
Step 2: Read the Sibling README.md FIRST (if present)
Before reading the spec itself, check for a sibling README.md in the same folder as the spec — i.e., <spec-path>/../README.md. This file is the wave-plan + spec-table that $joycraft-decompose writes per feature.
- If present: Read the README first. It tells you the spec's position in the wave plan, its dependencies, and which sibling specs (in the same folder) need to be done before this one.
- If absent: That's fine — proceed normally. The convention is forward-only and many legacy spec folders pre-date it.
Warn on Unmet Dependencies
If the README shows that this spec depends on other specs in the same folder, check whether those dependencies are satisfied. A dependency is satisfied once its frontmatter status: is in-review or done (see docs/reference/spec-status-lifecycle.md) — a checkpoint chain progresses on in-review without waiting for session-end to graduate it to done. A dependency still at todo is unmet.
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 · 155 lines · 29 tokens per session scan A 604aaa84a81b
joycraft-implement is a skill published in the GitHub repository maksutovic/joycraft (15 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 2,400 once invoked, about $0.0001 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
nextjs-patterns
Next.js App Router — Server Components, Actions, streaming, caching. Use when building or migrating Next.js apps.
vitest
Vitest unit testing — Vite-powered, Jest-compatible. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
frontend-coding
Expert frontend development guidance covering React, Vue, Angular, TypeScript, state management, component architecture, performance optimization, accessibility, testing, and modern web APIs. Produces production-ready, maintainable, and performant frontend code with best practices. Use when building web applications…
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-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-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", "уроки дизайна"…