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-bugfixnpx skills add maksutovic/joycraft --skill joycraft-bugfixgit 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-bugfix)<a href="https://agentmods.dev/skills/maksutovic/joycraft/joycraft-bugfix"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/joycraft-bugfix.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.00029 | $0.02631 |
| Opus 5 | $0.00015 | $0.01316 |
| Sonnet 5 | $0.00006 | $0.00526 |
| Haiku 4.5 | $0.00003 | $0.00263 |
Grade A, and why
joycraft-bugfix 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Workflow
You are fixing a bug. Follow this process in order. Do not skip steps.
Guard clause: If this is clearly a new feature, redirect to $joycraft-new-feature and stop.
Phase 1: Triage
Establish what's broken. Gather: symptom, steps to reproduce, expected vs actual behavior, when it started, relevant logs/errors. If an error message or stack trace is provided, read the referenced files immediately. Try to reproduce if steps are given.
Done when: You can describe the symptom in one sentence.
Phase 2: Diagnose
Find the root cause. Start from the error site and trace backward. Read source files — don't guess. Identify the specific line(s) and logic error. Check git blame if it's a recent regression.
Done when: You can explain what's wrong, why, and where in 2-3 sentences.
Phase 3: Discuss
Write this presentation to the style contract in docs/templates/reference/output-style.md.
Decide first — the pre-presentation rule
If the diagnosis contains any open question, or any load-bearing claim anchored
≤50, invoke $joycraft-decide on it NOW — before presenting. The Block Rule
(docs/context/anchors.md) fires pre-approval, every time; presenting
an artifact with open questions asks the human to approve an incomplete
artifact.
If the human already answered them in conversation, that counts as termination:
stamp the decisions: frontmatter and proceed — no dossier required. Zero open
questions and no ≤50 claims → the gate passes silently.
Present findings to the user BEFORE writing any code or spec:
- Symptom — confirm it matches what they see
- Root cause — specific file(s) and line(s)
- Proposed fix — what changes, where
- Risk — side effects? scope?
How to ask — the question directive. This governs every question moment in this skill: the Phase 1 triage clarifications and this Phase 3 confirmation. Every question is asked as structured forced-choice questions asked directly in chat: present the numbered options under the question, then wait for the answer before moving on. Never dump an unanswerable wall of open prose questions. Three rules ride on every question, no exceptions:
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 · 249 lines · 29 tokens per session scan A 393fe6351ba3
joycraft-bugfix is a skill published in the GitHub repository maksutovic/joycraft (15 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 2,631 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
pause
Stops current work on user request, captures full session state to project docs, and generates a resume prompt so the next session can continue without loss. Use when: "пауза", "стоп", "остановись", "stop", "pause", "подожди", "притормози", "сохрани прогресс", "прервись", "halt".
glyph
Render an answer as ASCII art plus semantic emojis inline, right now, with no setup questions. Use for a fast visual take on status, comparisons, trade-offs, architecture, or any ad-hoc 'show me X visually' ask. For a full multi-artifact plan playground, use visualize-plan instead.
quality-gates
Use when assessing task complexity, before starting complex tasks, when stuck after multiple attempts, or reviewing code against best practices. Provides quality-gates scoring (1-5), escalation workflows, and pattern library management.
session-summary
Use at the end of a work session on a DAE feature, so the next session picks up cleanly. Triggers — "/engineer.session-summary", "wrap up the session", "write the session log", "I'm stopping for the day".
configure
Interactive wizard for OrchestKit settings: MCP servers, hook permissions, keybindings, and install presets. Use when customizing plugin behavior or managing settings.
long-running-work-planning
Use this skill when facing long-running or heavy work that must continue without user intervention, especially large task decomposition, multi-task implementation, complex debugging, migrations, or work where context/tool limits are likely. It turns work into durable checkpoints so the agent can keep making progress…