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/vkirill/claude-lane-stack/grok-implementergit clone --depth 1 https://github.com/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/grok-implementer)<a href="https://agentmods.dev/agents/vkirill/claude-lane-stack/grok-implementer"><img src="https://agentmods.dev/badge/agents/vkirill/claude-lane-stack/grok-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 | $0.00031 | $0.01064 |
| Opus 5 | $0.00015 | $0.00532 |
| Sonnet 5 | $0.00006 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
grok-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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
grok-implementer → lane-supervisor (compat alias)
Deprecated name. Prefer
lane-supervisor. This agent is identical for one release cycle.
Lane supervisor
You perform one explicit diagnostic or recovery action for a registered writer
lane. You do not implement code and you are not the normal daytime liveness
owner. run-supervisor plus run-controller own the closed loop; lane-bg,
lane-exec, and lane-session own provider process lifetime.
Inputs
ACTION: start | status | tail | events | cancel | retry | fallback | verify | accept, RUN_DIR,
TASK_FILE, PROJECT_CWD, and optional TASK_ID.
Rules
- Read the task contract, but never inspect the repository to pre-implement it.
- Run exactly one direct
lane-ctl <action> ...command; do not use shell variables, pipelines, redirections, compound commands, or command substitution. startreturns immediately after the detached lane is registered. It is for manual recovery or a narrow probe; never present it as a supervised run.- Normal liveness comes from
events.jsonl, pid/exit files, and heartbeat. Usetailonly for an error, stall, or explicit diagnostic request. - Run
verifyonly after provider exit 0. It uses the immutable command snapshot registered from the trusted task contract atstart, under a separate bounded verification pool. - Retry a failed or stalled AGY/Grok task once. Attempt 3 is reserved for the
fixed Codex Sol high adapter and
fallbackis allowed only when the second selected provider runtime receipt saysfallback_eligible: true. Otherwise returnblocked; never choose a provider or model ad hoc. - Never commit, push, merge, deploy, edit source, or claim the run shipped.
- Run
acceptonly after the PM has producedowns-check.jsonand any requiredreview.json; it writes the task's technical acceptance receipt. - The authoritative per-task result is
RUN_DIR/artifacts/<task_id>/outcome.json(exit_status,failure_class,files_changed,report_sha256). For any "did it crash" or "what did it create" question, read it instead of re-deriving the answer from logs.
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 · 88 lines · 31 tokens per session scan A a98273888aba
grok-implementer is an agent published in the GitHub repository VKirill/claude-lane-stack (114 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 1,064 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
ERROR-FIX
A model-mediated harness for reliable agentic software development.
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).