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/commit-pushnpx skills add tykisgod/quick-question --skill commit-pushgit 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.00014 | $0.00850 |
| Opus 5 | $0.00007 | $0.00425 |
| Sonnet 5 | $0.00003 | $0.00170 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
commit-push 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 yesterday.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Script path fallback: qq scripts are invoked as bare commands (e.g.
unity-test.sh). If "command not found", use${CLAUDE_PLUGIN_ROOT}/bin/<command>instead.
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Batch commit all uncommitted changes and push to the remote repository.
Steps
-
If
qq-project-state.pyis available, run it first:qq-project-state.py --prettyInterpret it like this:
recommended_next == "/qq:commit-push"→ normal ship path, continue- otherwise → stop and tell the user the actual next step first
- if the user explicitly says to force the push anyway, note the risk and continue
-
Run
git status -uandgit diff --statto view all uncommitted changes -
Analyze the changes and group them by logical relationship (do not mix unrelated changes into the same commit):
- Feature code changes in one group (feat/fix/refactor)
- Asset files (prefabs, assets, scenes) in one group
- Config/docs in one group
- If all changes belong to the same feature, a single commit is fine
-
For each group:
git addthe relevant files (do not usegit add -A; specify files individually)- Write a commit message in conventional commit style
- Append
Co-Authored-By: Claude Opus 4.6 <[email protected]>at the end of the commit message
-
After all commits are done, run
git push -
Worktree closeout — detect worktree type and close out:
Type A: EnterWorktree session (CWD is inside
.claude/worktrees/):- Identify the source branch:
git log --oneline --all --decorate | head -5or read the branch the worktree was based on - Merge worktree branch back to source:
git checkout <source-branch> && git merge <worktree-branch> - Push source branch:
git push - Call
ExitWorktreetool withaction: "remove"to clean up and return to original CWD
Type B: qq-managed worktree (
qq-worktree.pyis available andisManagedWorktree=true):- Prefer one-step closeout:
qq-worktree.py closeout --auto-yes --delete-branch --pretty - If closeout refuses, inspect
qq-worktree.py status --pretty - Only fall back to separate
merge-back/cleanupwhen debugging
Type C: Not in a worktree → normal path, stop after push
- Identify the source branch:
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.
- yesterday First seen · 68 lines · 14 tokens per session scan A e0b8da0a98be
commit-push is a skill published in the GitHub repository tykisgod/quick-question (11 stars, last pushed 7d ago), licensed MIT. It adds 14 tokens to every session and 850 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
geometry-and-math
Use this skill when using Phaser 4 math and geometry utilities. Covers vectors, rectangles, circles, triangles, polygons, random number generation, angles, distance, interpolation, and snapping. Triggers on: Vector2, Rectangle, Circle, math, distance, angle, random, lerp.
text-and-bitmaptext
Use this skill when displaying text in Phaser 4. Covers Text game objects, BitmapText, web fonts, text styling, word wrap, alignment, padding, and dynamic text content. Triggers on: Text, BitmapText, this.add.text, font, word wrap, text style.
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-create-folder
Create a new folder under a parent folder inside 'Assets/'. The parent path must start with 'Assets/' and every intermediate folder in it must already exist. Refreshes the AssetDatabase at the end and returns the GUID(s) of the created folder(s).
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.