By yeaight7
Build and query graph-backed memory from mixed corpora (code, docs, images, video) to minimize token spend and avoid redundant file reads. Routes each corpus to the cheapest path: direct read, markdown conversion, graph build, graph update, or graph query.
Build or refresh graph-backed memory for a corpus, using graphify first and helper conversions only when they improve corpus quality.
Choose the cheapest context path across direct read, markdown conversion, graph build, graph update, or graph query.
Query an existing graphify graph before rereading the full corpus, using query, path, or explain flows.
Orchestrates graphify-centered memory build, refresh, and query flows for mixed corpora, using helper-tool preprocessing only when it materially improves graph input quality.
Recommends the cheapest direct-read, Markdown, graph build, update, or query path for a corpus while keeping graphify as the primary long-lived memory engine.
Use when the user provides a URL to a standard web page and clean Markdown extraction with Defuddle would reduce clutter and token cost.
any input (code, docs, papers, images) → knowledge graph → clustered communities → HTML + JSON + audit report. Use when the user wants to build, inspect, or query a cross-file knowledge graph from code, docs, papers, images, or videos with upstream graphify.
Use when the user provides a MarkItDown-supported file or URL and converting it to Markdown first will make inspection easier, cheaper, or more reliable.
Use when a user needs to build or refresh persistent graph memory from a mixed corpus and the right path may include graphify, incremental update, or helper conversion before ingestion.
Use when deciding the lowest-cost context path for a mixed corpus, especially when choosing among direct reading, helper conversion, graph build, graph update, or graph query.
Uses power tools
Uses Bash, Write, or Edit tools
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Oh My Zsh for coding agents.
Quickstart · Agent Quickstart · Plugins · Installation · Security Model · Contributing
Agent Powerups is an Oh My Zsh-style collection of reusable skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for coding agents.
Today, this repo ships:
apx) with runnable local checksapx plugins inspection (apx plugins list)apx profiles for curated skill/plugin setsNative install is direct for humans. Safety boundaries stay around external tools, secrets, shell profiles, and MCP enablement.
| Path | Status | Notes |
|---|---|---|
skills/ | shipped | Reusable agent workflows such as systematic-debugging and writing-plans |
mcp/ | shipped | Local-first GitHub MCP config with check, smoke, and explicit install commands |
agents-md/ | shipped | Starter AGENTS.md templates |
commands/ | shipped | Review-first command prompts plus safe runnable checks |
hooks/ | shipped | Review-before-use hook recipes plus safe runnable checks |
workflows/ | shipped | Scenario guides |
plugins/ | shipped | Plugins with local-first discovery, validation, native install, and marketplace metadata (apx plugins list) |
scripts/ | shipped | Validation and tool-check helpers for this repo |
examples/ | shipped | Minimal safe setup examples |
If you are an agent working in a repo with Agent Powerups available, route tasks to capabilities yourself instead of waiting to be told:
Match first. On Claude Code the host already lists skills natively — match the task to the narrowest fitting skill (plus obvious fits like no-fluff). On Codex, Gemini, or generic agents, start with apx discover.
Discover the rest — anything not natively loaded (MCP configs, hooks, AGENTS.md templates, installed-only assets):
apx discover "<the user's task>" --target <codex|claude-code|gemini|generic> --json
apx info <chosen-asset> # what it is, when to use it, source path, next action
Read, apply, verify. Read the asset's SKILL.md (or file) before applying it; run apx check <asset> only if it declares external requirements; then verify the result against the task.
Gate risky assets. MCP configs and hooks are review-before-use — surface them for approval, never auto-enable.
npm install -g agent-powerups
apx install claude --full
npx claudepluginhub yeaight7/agent-powerups --plugin memory-optimizationWorkflow-first MCP server design with schema-first tools, context-aware outputs, and evaluation discipline.
Browser, MCP, retrieval, and agent runtime integration skills with conservative setup and safety boundaries.
Quality gates for spec-driven development: adversarial plan verification and structured code review.
Documentation architecture, API reference authoring, ADR writing, readme hardening, and doc quality.
Multi-model orchestration and advisor routing: tri-model review and canonical advisor routing.
Ultra-compressed communication mode. Cuts 65% of output tokens (measured) while keeping full technical accuracy by speaking like a caveman.
Harness-native ECC plugin for engineering teams - 67 agents, 279 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
The Claude Code knowledge system — 380+ skills, 182+ agents, 100+ commands, 40 hooks, 32 rules, and workflows.