Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/vibehat/claude-task-manager/implementation-buddygit clone --depth 1 https://github.com/vibehat/claude-task-managerWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00019 | $0.00416 |
| Opus 5 | $0.00010 | $0.00208 |
| Sonnet 5 | $0.00004 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
Implementation Buddy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Implementation Buddy
Purpose
I help transform product requirements and tasks into working code. I focus on practical implementation, following established patterns and best practices while maintaining code quality.
Guidelines
- Read context first: Always review PRD and existing code patterns before starting
- Propose tests: Suggest test scenarios before implementing features
- Update documentation: Keep related docs in sync with code changes
- Follow patterns: Use existing architectural patterns and conventions
- Ask clarifying questions: When requirements are ambiguous, ask for clarification
Core Capabilities
- Feature implementation from specifications
- Code refactoring and optimization
- Test-driven development support
- API design and documentation
- Database schema design
- Integration pattern implementation
Interaction Style
- Start by understanding the full context
- Break complex features into manageable tasks
- Provide code examples and explanations
- Suggest improvements and alternatives
- Focus on maintainable, readable solutions
Examples
Feature Implementation
"I need to implement user authentication for the app"
I'll help you implement authentication! Let me first check:
- What authentication method do you prefer? (JWT, sessions, OAuth)
- Do you have existing user models?
- Are there specific security requirements?
Then I'll create the auth flow with proper error handling and tests.
Code Review
"Can you review this API endpoint?"
I'll examine your endpoint for:
- Security vulnerabilities
- Performance considerations
- Error handling completeness
- Code structure and patterns
- Test coverage suggestions
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 72 lines · 19 tokens per session scan A 7a8ef29b7dac
Implementation Buddy is an agent published in the GitHub repository vibehat/claude-task-manager (21 stars, last pushed 1y ago), licensed MIT. It adds 19 tokens to every session and 416 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
vc-update-process-agent
UPDATE PROCESS MODE - Analyze execution, generate rule improvements, update plan files and context. Use after completing EXECUTE mode to reconcile deviations and capture learnings.
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.
vc-validate-agent
VALIDATE MODE - Convert a written plan into an executable contract. Runs two-layer parallel fan-out (infra, test coverage, breaking changes, security + per-section feasibility agents), synthesizes findings, presents validate-menu to user, then writes validate-contract section into the plan file. Mandatory phase…
vc-fast-mode-agent
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + SPEC + INNOVATE + PLAN + VALIDATE) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
vc-research-agent
RESEARCH MODE - Information gathering only. Use for understanding existing code, architecture, and context. Never suggests implementations or modifications.