Agent
Use when an architectural choice or stage boundary needs a read-only view of invariants, ownership, extension seams, and proof.
27 20d ago A 30 tokens
original MIT
27Stars on the repository
32Mods indexed here, across every type
20d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown
code-mapper
02Agent
Use when quick reconnaissance is complete and an unfamiliar or risky bounded scope needs a read-only trace or thorough map of ownership, contracts, consumers, and unknowns.
27 20d ago A 36 tokens
original MIT
Agent
Use when a diff needs a read-only maintainability review for dead code, duplication, needless abstraction, reinvented primitives, and safe simplification.
27 20d ago A 34 tokens
original MIT
Agent
Use when documentation must be updated to accurately reflect verified repository behavior, tooling, installation, or operator workflows.
27 20d ago A 25 tokens
original MIT
Agent
Use when a proposed plan needs a read-only challenge of outcome, scope, acceptance, risk, and cheaper credible alternatives.
27 20d ago A 29 tokens
original MIT
Agent
Use when a feature or decision needs a read-only product lens on user goal, boundary, viable options, and tradeoffs.
27 20d ago A 30 tokens
original MIT
Agent
Use when a change or design needs a read-only adversarial review of trust boundaries, failures, state, persistence, concurrency, or replay.
27 20d ago A 33 tokens
original MIT
reviewer
08Agent
Use when a diff or delivered behavior needs a read-only correctness review for reachability, contract regressions, errors, and missing proof.
27 20d ago A 30 tokens
original MIT
Agent
Use when a delivered change needs a read-only check against the written task, acceptance criteria, explicit deferrals, and ownership boundaries.
27 20d ago A 32 tokens
original MIT
Agent
Use when a behavior change benefits from a narrow failing test before implementation and a test-only write scope is available.
27 20d ago A 28 tokens
original MIT