23,013 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Instructions for opensesh/KARIMO, covering karimo source repository rules, release protocol (mandatory), preferred method: release script, manual release checklist (if not using script) and critical: never move tags after release.
Important: ALL phases must use checkmarks for their tasks. Each checkmark should correspond to a single commit. The checkmark should be marked - [x] in the same commit that completes the task. Phase tasks should be prefixed with parent phase number and letters (a, b, c, etc.).
Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask in any language for code review, issue or PR triage, release gates, publishing follow-through, or project audits. Not for debugging root causes or prose review.
Discover dependencies and prepare or execute Kitaru core and plugin releases, including version proposals, Kitaru UI selection, release PRs, ordered tag commands, artifact verification, and recovery. Use when a user asks what a release depends on or wants to prepare, cut, publish, verify, or recover a Kitaru, Kitaru…
Release a new version of CodeMie CLI. Use when user says "release", "create release", "publish version", "bump version and release", or wants to publish a new version to npm. Handles version bumping, git tagging, pushing, and GitHub release creation with automatic version detection from conventional commits.
A guide for writing Git commit messages using Conventional Commits, a shared format that labels changes such as features, fixes, tests, documentation, and maintenance.
Kicks off a new AgentClinic feature by finding the next incomplete phase in specs/roadmap.md, creating a git branch, interviewing the user about scope/decisions/context, and writing a dated spec directory under specs/ containing plan.md, requirements.md, and validation.md. Trigger when the user says "feature spec"…
AGENTS.md instructions for taovc/pr-cockpit, covering pr-cockpit / pr cockpit, what this project is, running locally, constraints when changing code and frontend/ui conventions.
AGENTS.md instructions for kunchenguid/gh-axi, covering project agent memory, dependency bumps and the lockfile, the sdk-provided update command, release process and installable skill (src/skill.ts → skills/gh-axi/skill.md).
Claude Code instructions for alexarthurs/herdr-sidebar, covering herdr-sidebar monorepo, build / test / lint, plugin dev workflow, windows caveats (verified against herdr 0.7.1 and 0.8.x) and release flow (verified for v0.7.0).
Purpose: Button up everything at the end of a session — or before a /compact. Memories, plans, git — all tidy. Works for both closing out a chat and preparing for compaction.
Manages ghfs local mirror files in .ghfs/, especially translating user instructions into valid execute operations (execute.md, execute.yml, or per-item edits), running ghfs execute / ghfs sync, and validating issue/PR batch edits. Use when tasks involve editing issues/PRs through .ghfs artifacts, reconciling sync…
Claude Code instructions for Higangssh/homebutler, covering homebutler, verify before claiming anything works, writing commits, prs, and comments, no tool attribution and commit subjects.
Instructions for sahithvibudhi/vibe-tree, covering claude instructions, github actions failed build logs, electron app startup issues, launch with project and pull requests.
Upload local images and other files (PDF, zip, log, …) to GitHub and embed them in a pull request description, an issue, or a comment — producing canonical github.com/user-attachments URLs (private-repo uploads stay private). Use when asked to "attach a screenshot to the PR", "add an image to the PR description", "put…
Full release lifecycle — version bump, CHANGELOG, rich release notes, tag, publish. Use when user says "release", "tag and release", "publish version", "cut a release", "new version".
Run several independent Cotal features concurrently by creating one Git worktree and one spawn-capable mesh manager per feature; each manager staffs a review panel in a dedicated channel, adds one independent cold reviewer briefed under the cold-review skill, owns plan-to-commit delivery, and escalates unresolved…
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
★not rated 256▲
+9 4d agoA172 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: