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.
/plugin marketplace add tykisgod/quick-questionnpx agentmods add plugins/tykisgod/quick-question/quick-questiongit clone --depth 1 https://github.com/tykisgod/quick-questionGrade A, and why
qq 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.
What it actually says
{
"name": "qq",
"version": "1.17.0",
"description": "The control plane for game-dev agents — close the loop with verified compile, test, and cross-model review across Unity, Godot, Unreal, and S&box. Lifecycle-aware /qq:go routing, structured runtime state in .qq/, 26 /qq:* slash commands. Claude Code-first, agent-agnostic via HTTP and MCP.",
"author": {
"name": "Yukang Tian",
"url": "https://github.com/tykisgod"
},
"homepage": "https://github.com/tykisgod/quick-question",
"repository": "https://github.com/tykisgod/quick-question",
"license": "MIT",
"keywords": [
"unity",
"unity-editor",
"game-development",
"gamedev",
"csharp",
"C#",
"auto-compile",
"compilation",
"testing",
"unit-test",
"editmode",
"playmode",
"code-review",
"cross-model-review",
"codex",
"hooks",
"skills",
"tykit",
"lifecycle",
"workflow",
"macos"
]
}
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 36 lines scan A e0cc2acf9f20
qq is a plugin published in the GitHub repository tykisgod/quick-question (11 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
awesome-gamedev-agent-skills
Plugin marketplace listing 10 plugins: gamedev, router, godot, unity, unreal.
summer-engine-agent
Agent tooling for Summer Engine: game-dev skills, lifecycle hooks, and a 58-tool MCP bridge to the local desktop app.
bevy-plugin
Bevy game engine development - ECS, rendering, game architecture.
godot
Develop, test, build, and deploy Godot 4.x games. Includes GdUnit4 testing, PlayGodot automation, web/desktop exports, CI/CD pipelines, and deployment.
dmitriy-claude-plugins
Personal collection of Claude Code plugins for development workflows and productivity.
bevy-skills
AI agent skills for Bevy 0.19: ECS, rendering, physics, input, assets, audio, accessibility, persistence, testing, profiling, voxels, and migration.