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/tykisgod/quick-question/bootstrapnpx skills add tykisgod/quick-question --skill bootstrapgit clone --depth 1 https://github.com/tykisgod/quick-questionWhat 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.00056 | $0.01289 |
| Opus 5 | $0.00028 | $0.00645 |
| Sonnet 5 | $0.00011 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
bootstrap 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Take a high-level game vision and turn it into a structured, executable project — decomposing pillars into epics, then driving each through the qq pipeline.
Arguments: $ARGUMENTS (a description, a file path to a pitch/checklist document, or empty for interactive)
Phase 1: Understand the Vision
Read the input. Extract:
- Pillars — the 3-5 non-negotiable design pillars (e.g., "turn-based PVP", "simple multiplayer", "WWII theme")
- Fragment rules — specific details mentioned in passing (unit types, reference games, feel descriptions)
- Reference games — any games mentioned as inspiration
Then ask about gaps, using these preset directions (ask only what's missing, skip what's already covered):
- Target experience — "What should 10 minutes of gameplay feel like?" (if not clear from input)
- Scope — "Is this a full game or a playable demo/prototype? How many sessions to reach 'done'?"
- Platform & tech — engine, target platform, multiplayer architecture (if not obvious from project context)
- Art direction — placeholder/greybox or specific style? (if relevant)
- Hard constraints — budget, timeline, team size, must-use systems
Max 5 questions total. Make reasonable assumptions for non-critical unknowns.
Phase 2: Decompose into Epics
Break the vision into epics — each a self-contained vertical slice that can go through the full qq pipeline independently.
Rules:
- Each epic should be completable in 1-3 qq pipeline runs (design → plan → execute → test)
- Epics have explicit dependencies: which must finish before which can start
- Flag which epics can run in parallel
- Order by: dependencies first, then core-to-peripheral (get the core loop working before polish)
Output a manifest file and save to Docs/qq/<branch-name>/bootstrap-manifest.md.
Present to user for confirmation. This is the key human checkpoint — user approves the breakdown before automation begins.
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 First seen · 117 lines · 56 tokens per session scan A 79d929e789ba
bootstrap is a skill published in the GitHub repository tykisgod/quick-question (11 stars, last pushed 8d ago), licensed MIT. It adds 56 tokens to every session and 1,289 once invoked, about $0.0003 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
unity-mcp-orchestrator
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for…
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
assets-prefab-save
Save the currently opened prefab edit stage back to its prefab asset without exiting the stage. Pair with 'assets-prefab-open' to enter the edit mode first.
mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
build-game-monster-system
Build, integrate, audit, or refactor rigged monsters for Three.js and web action games. Use for monster asset contracts, procedural or imported creature rigs, semantic joints and sockets, hurtboxes and attack volumes, combat animation states, enemy-runtime adapters, LODs, deterministic review fixtures, and validating…
design-game-encounters
Design, implement, tune, or test Three.js action-game encounters. Use for arena layout, enemy composition, spawn pacing, objectives, boss phases, reward cadence, encounter fixtures, and difficulty validation.