Per-IDE setup walkthroughs for using @mongez/agent-kit with Claude Code, Cursor, Codex, Kiro, Gemini CLI, GitHub Copilot, Aider, and Antigravity. Each walkthrough shows the exact files agent-kit creates, the --target flag to pass, the reload quirks, and a copy-pasteable package.json snippet.
Scaffold the AI-assisted coding governance package into a target project repository — copies the two entry files (AGENTS.md at the root and a thin CLAUDE.md) plus the companion rule files into an ai-governance/ directory, then interviews the user to fill in the placeholders and to author the active client's profile.…
A set of instructions for creating and maintaining Forge plugins. Forge plugins are local extensions that can add tools, commands, and other integration points to Forge.
Lightweight smart project memory for Codex. Use when the user wants to initialize or maintain persistent Codex project memory, create a multi-project workspace, add a new project with reusable context files, recover context in new chats, write session snapshots, compact important conclusions into durable files, route…
Work on code-agnostic, the CLI that centralizes MCP servers, rules, skills, agents, and workspace config, then compiles and syncs them into Codex, Cursor, and OpenCode. Use when editing this repo, explaining how code-agnostic works, or changing its config compiler, import, plan, apply, status, workspace, rule, skill…
Design and generate AI Agent role/personality definitions using the SOUL/IDENTITY/AGENTS three-layer prompt architecture. Use when: (1) Creating a new AI Agent persona from scratch, (2) Writing or editing SOUL.md, IDENTITY.md, or AGENTS.md files, (3) Designing role prompts for AI assistants, chatbots, or autonomous…
Initialize or update repository-level agent operating instructions, AGENTS.md, quality workflow docs, execution-plan templates, and harness guidance for an AI-agent-driven software project. Use when Codex is asked to set up a new repository for agent-driven development, bootstrap or merge AGENTS.md, auto-select…
Audit and optimize OpenClaw workspace documents (AGENTS.md, SOUL.md, USER.md, TOOLS.md, IDENTITY.md, HEARTBEAT.md, BOOT.md, MEMORY.md, memory/) for redundancy, dead content, format compliance, cross-file conflicts, and token efficiency. Use when user asks to audit workspace files, check document health, reduce token…
Repository harness for agentic software development. Use when the user wants a repo to follow Harness Engineering or harness-first coding practices, asks to bootstrap or maintain AGENTS.md, architecture docs, execution plans, verification loops, repo-local automation, or requests harness-first setup for future…
Use GovernSpec to work with local-first AI task contracts. Trigger when a repository contains govern.yaml, .govern.yaml, kind GovernSpec, or kind GovernPack; when Codex needs to validate or inspect a task contract; compile contracts to AGENTS.md, prompts, OpenAI structured outputs, MCP plans, or generic skill bundles…
A workflow for a main coding agent to coordinate smaller agents that search, edit code, and run commands. It defines how tasks are split, how progress is reported, and what happens when an agent fails.
MANDATORY for starting any conversation or task. Establishes required workflows: discovering and using skills, invoking the Skill tool before announcing usage, performing brainstorming before coding, creating TodoWrite todos for all checklists, and selecting/invoking the correct specialized agent persona for the task…
A software-engineering approach for preparing a code repository so an AI agent can work through tasks independently. It combines clear rules, useful documentation, automated feedback such as tests and CI, and checks that verify the result.
Research the project and generate a holistic AGENTS.md file at the repo root. Use when the user says "init agents.md", "create AGENTS.md", or the project lacks agent instructions.
Generate copy-paste bash scripts for Ralph Wiggum/AI agent loops (Codex, Claude Code, OpenCode, Goose). Use when asked for a "Ralph loop", "Ralph Wiggum loop", or an AI loop to plan/build code via PROMPT.md + AGENTS.md, SPECS, and IMPLEMENTATIONPLAN.md, including PLANNING vs BUILDING modes, backpressure, sandboxing…
Use when starting, restructuring, or maintaining a project repository that needs durable Codex guidance, clear document ownership, requirements and acceptance records, current-state tracking, verification contracts, and an auditable work log.
Audit and govern local Codex architecture. Use when the user asks where to store or configure AGENTS.md rules, project knowledge, memories, skills, SKILL.md files, references, hooks, subagents, plugins, MCP servers, connectors, ECC assets, context management, or Codex architecture diagrams; when creating or updating…
Bootstrap a tool-agnostic AI workflow environment based on the AGENTS.md open standard. Use whenever the user wants to set up, scaffold, initialize, install or configure a new project (or a fresh machine) for AI coding agents — Claude Code, Codex, Cursor, Windsurf, Gemini CLI, Antigravity, OpenCode, Aider, Zed, Warp…
Bootstrap a reusable repository documentation hierarchy for AI agents. Use when starting a new project, initializing repo docs, setting up CLAUDE.md and AGENTS.md, defining L1/L2/L3 documentation layers, creating AGENTS.md symlinks, or designing a fractal documentation system that helps AI quickly understand and…
Standardize lightweight AI collaboration and development workflows for a code repository. Use when the user asks to create or improve AGENTS.md, AI coding guidelines, project iteration workflow, Current/Proposal process, direct/brief/standard/decision task levels, dev-log, project-state, automatic project memory…
Index/map of AI agent skills published under GitHub user bigdata2211it-web. For each skill: a link to its GitHub repo and a one-line description. Use when the user asks "what skills are there", "show me all skills", "give me the github link for skill X", or when an agent needs to know which skill covers a task.
★not rated 2 3mo agoA78 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: