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 instructions/techymt/claude-code-superpowers/gemini-mdgit clone --depth 1 https://github.com/TechyMT/claude-code-superpowersWhat 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.00341 | $0.00341 |
| Opus 5 | $0.00170 | $0.00170 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
claude-code-superpowers GEMINI.md 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.
What it actually says
Claude Code Superpowers — Gemini CLI
Gemini CLI loads skills once at session start by reading this file — every @ line below is
inlined into your context before your first prompt. This differs from trigger-based agents
(Claude Code, Cursor) where skills load on demand as your prompt matches their description
field. The trade-off: Gemini always has the full context but uses more tokens per session;
trigger-based agents are leaner but require a matching prompt to activate a skill.
Remove @ lines for skills you don't need to reduce context size. A good starting set is
domain-model, error-handling, and whichever skill matches your current task.
Each line below loads a skill into your Gemini CLI context. Remove lines for skills you don't need.
@./skills/domain-model/SKILL.md @./skills/error-handling/SKILL.md @./skills/types-and-interfaces/SKILL.md @./skills/tool-definition/SKILL.md @./skills/permission-system/SKILL.md @./skills/async-concurrency/SKILL.md @./skills/build-tool-factory/SKILL.md @./skills/module-organisation/SKILL.md @./skills/naming-conventions/SKILL.md @./skills/hot-paths/SKILL.md @./skills/state-management/SKILL.md @./skills/task-system/SKILL.md @./skills/system-boundaries/SKILL.md @./skills/observability/SKILL.md @./skills/skill-and-command-dispatch/SKILL.md @./skills/creating-skills/SKILL.md
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 · 30 lines · 341 tokens per session scan A 975abc098e1f
claude-code-superpowers GEMINI.md is an instructions file published in the GitHub repository TechyMT/claude-code-superpowers (5 stars, last pushed 5mo ago), licensed MIT. It adds 341 tokens to every session, about $0.0017 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-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.