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-featurenpx skills add maksutovic/joycraft --skill joycraft-implement-featuregit 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-feature)<a href="https://agentmods.dev/skills/maksutovic/joycraft/joycraft-implement-feature"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/joycraft-implement-feature.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.00034 | $0.00964 |
| Opus 5 | $0.00017 | $0.00482 |
| Sonnet 5 | $0.00007 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
joycraft-implement-feature 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Feature (Whole-Queue Driver)
One invocation runs a feature's whole spec queue: $joycraft-implement-feature docs/features/<slug>/. You drive the queue sequentially in this conversation — Codex has no subagent boundary to give each spec a fresh context, so the chain shares context and compensates with disciplined per-spec wrap-ups. This is ordinary interactive use — one human invocation, no headless loop, no ToS/cost caveat.
Context honesty: for queues of heavy
isolated-mode specs, a shared-context chain is the wrong tool — true per-spec isolation comes from Pi'sjoycraft-implement-loop(fresh process per spec) or guided-manual (/new+ re-invoke per spec). Say so up front when you see a queue dominated byisolatedspecs, then proceed only if the user confirms.
Step 1: Load the Queue
-
Resolve the specs directory: if the given path contains a
specs/subdirectory, use it; otherwise use the path itself. Look for.joycraft-spec-queue.jsonthere. -
No queue → stop:
No spec queue found in [path]. Run
$joycraft-decomposefirst — it writes the queue, the specs, and the wave plan. -
Read the sibling
README.md(the wave plan) for the intended order. Waves marked parallel-safe still run sequentially here — parallelism needs isolation this harness chain doesn't have. -
Report the plan before starting: feature slug, M specs, current statuses, the order you'll run them in. If the queue is dominated by
isolatedspecs, surface the context-honesty note above and get a confirmation. -
If no
todospecs remain, skip to Step 4 and say why.
Step 2: The Chain — One Spec at a Time
Repeat until no todo specs remain:
- Find the next ready spec: the first
todowhosedepends_onare allin-review/done(read the queue JSON). - None ready but
todospecs remain → fail-fast (Step 3): report which specs are blocked and on what. - Execute the spec by following
.agents/skills/joycraft-implement/SKILL.mdend to end — strict TDD (failing tests first, implement until green, every Acceptance Criterion met), then its per-spec wrap-up: bump toin-reviewin BOTH the queue JSON and the spec's frontmatter, terse discovery stub only if surprised, commitspec: <spec-name>. (Treatisolatedspecs the user approved into this chain ascheckpoint.) - Verify before advancing: queue shows
in-review,git logshows thespec:commit, tests green. Anything off → fail-fast (Step 3). - Report one line —
Spec complete: <name> (spec N of M)— and continue.
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 · 55 lines · 34 tokens per session scan A 54036db549ec
joycraft-implement-feature is a skill published in the GitHub repository maksutovic/joycraft (15 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 964 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".
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…
code-reviewing
Code review methodology and quality standards for comprehensive code analysis. Use to understand WHAT and HOW to review code: 11 review dimensions, process, quality standards. Use when: "проверь код", "code review", "ревью кода", "review this code", "check code quality".
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: "сделай…