loc-guardian
Enforces per-file lines-of-code limits, flags violations, and provides opus-powered extraction plans.
🛡️ AgentReady threat assessment
MAESTRO 7-layer threat model + OWASP AIVSS risk score for loc-guardian, derived from its capabilities.
These scores are auto-generated from public information (the agent's own listing, docs, and repository) using the canonical OWASP AIVSS formula and the MAESTRO framework — an estimate for guidance, not a penetration test, audit, or certification. See the scoring methodology — every score is re-derived by the same automated method as an agent's public evidence changes.
Overview
A Claude Code plugin that enforces pure lines-of-code limits per file using tokei, flags violations, and generates Opus-powered extraction plans to split oversized files. Runs as a hook on Write/Edit to count LOC and gate changes, giving it a place on the file-write path.
Key features and capabilities
- Per-file LOC limits via tokei
- Violation flagging on write
- Opus-powered extraction plans
Use cases
- Keep files under size limits
- Plan refactors for oversized files