Discipline + security starter kit that keeps Claude Code (or any LLM agent) on course across sessions: repo-based memory that survives compaction, enforced hooks & permissions, and a phased workflow — consistent, traceable, safe. Clone it or install as a plugin.
Subagents are isolated assistants for side tasks (deep research, audits, verification) that would clutter the main thread with intermediate results you won't reference again. Each runs in its own context window and returns only its final message to the parent — so the raw exploration never enters your main context.…
Read-only rules-compliance auditor — samples a commit range against rules.md (layout §3, security §5/§7, tests §2, docs-sync §1, memory §9) and returns violations with file:line + the rule §, severity-ranked. Reports only, never edits. Spawned by /keel-audit; the SessionStart hook nudges when one is due.
Isolated external-research agent — scans the web and the local repo for prior art, returns a distilled, CITED findings summary (not raw pages). Use when a question needs docs/papers/GitHub/community input that would clutter the main thread. Backs rules.md §8 and the /keel-research skill.
Adversarial verification agent — given a claim, finding, or proposed fix, tries to REFUTE it (reproduce the failure, run the test, read the code) and returns CONFIRMED / REFUTED / UNCERTAIN with evidence. Use to check sub-agent output, review findings, or "is this actually true?" before acting. Backs rules.md §4 and…
Owner-triggered independent process & quality critic — the project's OUTSIDE EYE. Sits outside the agent team, is never spawned by the orchestrator, and questions the rules themselves; rule COMPLIANCE is /keel-audit's job, not this one's.
★not rated 9 22d agoA56 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: