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-gather-contextgit 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-gather-context)<a href="https://agentmods.dev/skills/maksutovic/joycraft/joycraft-gather-context"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/joycraft-gather-context/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-gather-context"><img src="https://agentmods.dev/badge/skills/maksutovic/joycraft/joycraft-gather-context.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.00042 | $0.01594 |
| Opus 5 | $0.00021 | $0.00797 |
| Sonnet 5 | $0.00008 | $0.00319 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
joycraft-gather-context 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 2d 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 — 87 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.
Gather Context
This is the first-run read-then-offer onboarding pass — the lowest-intervention way to populate the project's context layer. You read what context already exists, summarize coverage, offer a gap-only interview, and write everything in one reviewable batch at the end.
This skill is self-contained. It composes the same conventions the single-doc skills use, but everything you need is inlined below — do not call into or import another skill's logic.
Step 1: Read What Already Exists First
The user has invoked the first-run onboarding pass (e.g., $joycraft-gather-context). Before asking the user anything, scan the project's existing context. Default scan breadth is README + docs/ + AGENTS.md only:
- The README(s) at the repo root and any obvious sub-package READMEs.
docs/**— existing design, architecture, or style docs.docs/context/*— the flat operational fact-docs (production-map, dangerous-assumptions, decision-log, institutional-knowledge, troubleshooting) anddocs/context/reference/*long-form docs.- The current AGENTS.md content, including any
## Context Mapsection.
Then summarize for the user what context already exists and what's covered.
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.
- 2d ago Changed · +2 lines 18b228d0c63f
- 5d ago Changed · +17 lines 9e1785b6f038
- 10d ago First seen · 68 lines · 42 tokens per session scan A 2c6ac1e77c7d
joycraft-gather-context is a skill published in the GitHub repository maksutovic/joycraft (15 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 1,594 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
qamap-pr-qa
Local zero-LLM PR QA workflow. Use when an agent is preparing, updating, finalizing, or reviewing a pull request, asks what the PR should test, or needs commit-backed change intent, affected behavior, QA scenarios, evidence, validation commands, optional automation drafts, and manifest repair guidance.
NestJS Framework
Node.js/TypeScript backend framework with dependency injection and modular architecture.
using-prisma
Prisma 5+ ORM with schema-first design, type-safe client, migrations, and database integrations (Supabase, PlanetScale, Neon). Use for TypeScript/JavaScript database access.
PR Etiquette
This skill should be used when responding to maintainer review feedback, writing or reviewing PR descriptions, following up on dormant PRs, validating PR quality before submission, or deciding how to communicate with maintainers. Sibling to oss-contribution and contribution-ethics.
async-await-patterns
Use when writing JavaScript or TypeScript code with asynchronous operations, fixing promise-related bugs, or converting callback/promise patterns to async/await. Triggers: 'promise chain', 'unhandled rejection', 'race condition in JS', 'callback hell', 'Promise.all', 'sequential vs parallel async', 'missing await'.…
session-manager
A fallback skill for recording development sessions and restoring project context from an Obsidian vault, a folder of linked notes. It handles explicit resume, handoff, status, and end-of-session requests when automatic capture is unavailable.