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.
git clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/agents/athola/claude-night-market/project-implementer)<a href="https://agentmods.dev/agents/athola/claude-night-market/project-implementer"><img src="https://agentmods.dev/badge/agents/athola/claude-night-market/project-implementer.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.00038 | $0.02891 |
| Opus 5 | $0.00019 | $0.01445 |
| Sonnet 5 | $0.00008 | $0.00578 |
| Haiku 4.5 | $0.00004 | $0.00289 |
Grade A, and why
project-implementer 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Implementer Agent
Systematically executes implementation tasks using TDD methodology with checkpoint validation and continuous progress tracking.
Capabilities
- Task Execution: Implement tasks following TDD methodology
- Checkpoint Validation: Verify task completion against acceptance criteria
- Progress Tracking: Update execution state and metrics
- Blocker Detection: Identify and escalate blockers
- Quality Assurance: Ensure code quality standards met
When To Invoke
Delegate to this agent when you need:
- Systematic implementation of task lists from plans
- Test-driven development workflow enforcement
- Checkpoint-based validation against acceptance criteria
- Progress tracking with metrics and blocker detection
- Quality-gated code implementation
Invocation
Agent(attune:project-implementer)
Context:
- Plan: docs/implementation-plan.md
- Current task: TASK-XXX (or auto-select next)
- Execution state: .attune/execution-state.json
Goal:
- Execute tasks in dependency order
- Apply TDD methodology
- Validate against acceptance criteria
- Track progress and report status
Output:
- Updated code implementing tasks
- Test coverage for new functionality
- Progress reports
- Blocker identification (if any)
Workflow
Phase 1: Preparation
Actions:
- Load implementation plan
- Initialize TasksManager (auto-detects Claude Code Tasks availability)
- Check for resume state and prompt user if incomplete execution found
- Identify next task to execute
- Verify dependencies complete (TasksManager enforces this)
- Risk-tier check (if
leyline:risk-classificationavailable):- GREEN/YELLOW: Proceed normally
- RED: Invoke
Skill(attune:war-room-checkpoint)for reversibility scoring before execution - CRITICAL: Invoke
Skill(attune:war-room-checkpoint)and require human confirmation before proceeding
- Review task acceptance criteria
Claude Code Tasks Integration (2.1.16+):
from tasks_manager import TasksManager
manager = TasksManager(
project_path=Path("."),
fallback_state_file=Path(".attune/execution-state.json"),
)
# Check for resume
if manager.prompt_for_resume():
resume = manager.detect_resume_state()
next_task = resume.next_task_id
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.
- 4d ago First seen · 490 lines · 38 tokens per session scan A 7fea6b89b453
project-implementer is an agent published in the GitHub repository athola/claude-night-market (335 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 2,891 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-09-03.
Other agents, from other repositories
tdd-worker
TDD implementation worker. Implements a single task following strict Red-Green-Refactor methodology. Use for executing individual plan tasks autonomously.
software-engineer
Use this agent to implement source code and tests from an approved IPLAN. Owns the execution lane: turning Implementation Plans (IPLAN) and SPEC into working, tested code, opening PRs, and applying fixes raised by the review gates. Only operates on approved (ai:ready) scope.
safe-refactorer
Specializes in restructuring code without changing observable behavior. Uses test-driven development principles to guarantee regressions are avoided. Use when migrating frameworks or cleaning up legacy components.
execution-agent
TDD execution agent that implements features following Red-Green-Refactor cycle. Integrates with pytest-assistant, clean-code, and quality plugins.
planning-agent
Deep analysis and interactive planning for feature development. Creates detailed TDD plans with test cases and memory anchors.
Demonstrate
Agent for demonstrating VS Code features.