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 maksutovic/joycraft --skill joycraft-spec-donegit 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-spec-done)<a href="https://agentmods.dev/skills/maksutovic/joycraft/joycraft-spec-done"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/joycraft-spec-done/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/maksutovic/joycraft/joycraft-spec-done"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/joycraft-spec-done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01052 |
| Opus 5.5 | $0.00018 | $0.00421 |
| Sonnet 5.5 | $0.00009 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
joycraft-spec-done 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
At skill entry, run node docs/.joycraft/check.mjs check --json --session <session-id> once, reusing JOYCRAFT_SESSION_ID if supplied or one ID chosen for this conversation. If the checker is missing or fails, continue the requested skill quietly without retrying setup. Offer updates only for display: true; current, postponed, off, and unknown stay quiet. If automaticUpdate is present, finish this skill, then run its exact command once from the project root: the candidate must verify every safety gate before applying. Other updates require approval. After an offer or automatic attempt, record it with node docs/.joycraft/check.mjs acknowledge <available-version> --session <session-id>. Apply updates only at this workflow boundary; after success, reinvoke the skill or restart the session to load changed instructions.
Spec Done (Lightweight Per-Spec Wrap-Up)
You just finished implementing one atomic spec. This is the fast handshake that runs once per spec, before context clears — the todo → in-review transition in the lifecycle (docs/reference/spec-status-lifecycle.md). It is deliberately tiny: it does exactly four things and nothing more.
This is NOT session-end. It does not run validation, push, or open a PR. It trusts the TDD you just did in
joycraft-implement. The heavy once-per-feature wrap-up (full validation + consolidate discoveries + push + PR) isjoycraft-session-end, which runs once at the end of the feature.Usually you don't run this by hand:
joycraft-implementperforms these four steps itself at the end of every checkpoint/isolated spec (andjoycraft-implement-featuredrives whole queues). This skill remains the canonical definition of the wrap-up — run it manually after ad-hoc work done outside the implement skill, or when an implement run was interrupted before wrapping up.
Step 1: Bump status to in-review — in BOTH systems
A spec's status lives in two places that must never disagree (the desync this feature exists to kill): the queue JSON and the spec's frontmatter. Update both to in-review.
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.
- 1mo ago Changed · +2 lines 35dc99b7feaa
- 1mo ago First seen · 61 lines · 46 tokens per session scan A 4018ed142f00
joycraft-spec-done is a skill published in the GitHub repository maksutovic/joycraft (15 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,052 once invoked, about $0.0002 per session on Opus 5.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
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.