zap-coding-agent
Reduces token consumption and latency in AI-assisted development by indexing code structure locally, lowering operational costs and enabling faster iteration…
ZAP is a terminal-first, local AI coding agent built in Rust. It uses AST-powered codebase indexing and lazy-loaded skills to completely eliminate prompt bloat and minimize context token costs.
- Ask Claude to analyze your codebase structure and identify architectural inconsistencies quickly.
- Generate refactoring suggestions for legacy code without sending entire files to the model.
- Automate routine code reviews by scanning diffs against your project's coding standards locally.
Reduces token consumption and latency in AI-assisted development by indexing code structure locally, lowering operational costs and enabling faster iteration on large codebases.
Engineering teams managing large Rust or polyglot codebases seeking cost-efficient local AI coding assistance without cloud dependencies.
https://github.com/zap-coding-agent/zap-coding-agent
By zap-coding-agent
How to Get It
claude plugins install zap-coding-agent/zap-coding-agent
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Analyze my codebase structure and identify architectural inconsistencies quickly
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 25 GitHub stars; 1 contributors; last commit 1d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 25 GitHub stars; 1 contributors; last commit 1d ago; license no license.