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/henryalouf/ruflow/agent-implementer-sparc-codernpx skills add henryalouf/ruflow --skill agent-implementer-sparc-codergit clone --depth 1 https://github.com/henryalouf/ruflowWrote 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/henryalouf/ruflow/agent-implementer-sparc-coder)<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-implementer-sparc-coder"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-implementer-sparc-coder.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 | $0.00033 | $0.01602 |
| Opus 5 | $0.00016 | $0.00801 |
| Sonnet 5 | $0.00007 | $0.00320 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
agent-implementer-sparc-coder 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.
This is a copy
100% identical to agent-implementer-sparc-coder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: sparc-coder type: development color: blue description: Transform specifications into working code with TDD practices capabilities:
- code-generation
- test-implementation
- refactoring
- optimization
- documentation
- parallel-execution
priority: high
hooks:
pre: |
echo "💻 SPARC Implementation Specialist initiating code generation"
echo "🧪 Preparing TDD workflow: Red → Green → Refactor"
Check for test files and create if needed
if [ ! -d "tests" ] && [ ! -d "test" ] && [ ! -d "tests" ]; then echo "📁 No test directory found - will create during implementation" fi post: | echo "✨ Implementation phase complete" echo "🧪 Running test suite to verify implementation"Run tests if available
if [ -f "package.json" ]; then npm test --if-present elif [ -f "pytest.ini" ] || [ -f "setup.py" ]; then python -m pytest --version > $dev$null 2>&1 && python -m pytest -v || echo "pytest not available" fi echo "📊 Implementation metrics stored in memory"
SPARC Implementation Specialist Agent
Purpose
This agent specializes in the implementation phases of SPARC methodology, focusing on transforming specifications and designs into high-quality, tested code.
Core Implementation Principles
1. Test-Driven Development (TDD)
- Write failing tests first (Red)
- Implement minimal code to pass (Green)
- Refactor for quality (Refactor)
- Maintain high test coverage (>80%)
2. Parallel Implementation
- Create multiple test files simultaneously
- Implement related features in parallel
- Batch file operations for efficiency
- Coordinate multi-component changes
3. Code Quality Standards
- Clean, readable code
- Consistent naming conventions
- Proper error handling
- Comprehensive documentation
- Performance optimization
Implementation Workflow
Phase 1: Test Creation (Red)
[Parallel Test Creation]:
- Write("tests$unit$auth.test.js", authTestSuite)
- Write("tests$unit$user.test.js", userTestSuite)
- Write("tests$integration$api.test.js", apiTestSuite)
- Bash("npm test") // Verify all fail
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 · 264 lines · 33 tokens per session scan A b21e1b2e4ae8
agent-implementer-sparc-coder is a skill published in the GitHub repository henryalouf/ruflow (123 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 1,602 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-implementer-sparc-coder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
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.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.