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 skills/rsts-dev/claude-buddy-marketplace/implementationnpx skills add rsts-dev/claude-buddy-marketplace --skill implementationgit clone --depth 1 https://github.com/rsts-dev/claude-buddy-marketplaceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rsts-dev/claude-buddy-marketplace/implementation)<a href="https://agentmods.dev/skills/rsts-dev/claude-buddy-marketplace/implementation"><img src="https://agentmods.dev/badge/skills/rsts-dev/claude-buddy-marketplace/implementation.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00047 | $0.00486 |
| Opus 5 | $0.00023 | $0.00243 |
| Sonnet 5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
Implementation 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 5d 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
Execute tasks from tasks.md following TDD workflow with phase-by-phase execution, progress tracking, and completion validation.
Customization
Before executing, check for user customizations at:
~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Implementation/
If this directory exists, load and apply any PREFERENCES.md configurations. If not, proceed with defaults.
Prerequisites
- LifeOS must be installed. Check
~/.claude/LIFEOS/VERSION. - Foundation must exist at
/directive/foundation.md. - Tasks must exist in
specs/directory.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| ExecuteTasks | Any invocation | Workflows/ExecuteTasks.md |
Task Discovery
Scans specs/ for folders containing tasks.md. If multiple found, asks user which to execute.
Execution Model
- Phase-by-phase: Setup -> Tests (TDD) -> Core -> Integration -> Polish
- TDD: Tests MUST fail first (red), then pass after implementation (green)
- Progress: Updates checkboxes in
tasks.mdafter each completed task - Errors: Halts on sequential task failure; continues on parallel
[P]failure
Output
Updates tasks.md in-place with completion checkboxes. Changes status to "Completed" when done.
Examples
Example 1: Execute implementation
User: "/buddy:implement"
-> Discovers specs/20260402-user-authentication/tasks.md
-> Reads all design documents (spec, plan, tasks, data-model, etc.)
-> Executes Phase 3.1 Setup tasks
-> Executes Phase 3.2 Tests (expects failures - TDD red)
-> Executes Phase 3.3 Core (tests should pass - TDD green)
-> Executes Phase 3.4 Integration, Phase 3.5 Polish
-> Updates tasks.md checkboxes throughout
-> Reports completion summary
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 58 lines · 47 tokens per session scan A e8c356e442ed
Implementation is a skill published in the GitHub repository rsts-dev/claude-buddy-marketplace (17 stars, last pushed 14d ago), licensed MIT. It adds 47 tokens to every session and 486 once invoked, about $0.0002 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 skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.