agent-memory-kit
It enables structured multi-agent orchestration and persistent state management through file-based memory.
Multi-Agent Driven Development Kit for Claude Code: you talk to one agent, it runs the team — a main session orchestrates full sessions and their subagents through brief, report and acceptance files; memory as plain dated files lets any session be cleared without losing the work.
- Automate complex development tasks by delegating work to a team of subagents
- Maintain project context across different sessions using plain text memory files
- Generate progress reports and acceptance files to track multi-agent workflows
It enables structured multi-agent orchestration and persistent state management through file-based memory. This reduces context loss during long-running development cycles and ensures continuity across disparate agent sessions.
Engineering leads implementing complex, multi-agent workflows that require persistent state and structured handoffs between specialized sub-agents.
https://github.com/awrshift/agent-memory-kit
By awrshift
How to Get It
claude plugins install awrshift/agent-memory-kit
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:
Help me automate complex development tasks by delegating work to a team of subagents
Trust Signals Auto-scanned
Community Pulse Quiet
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): 34 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
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.
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): 34 GitHub stars; contributors unknown; last commit 0d ago; license MIT.