A coding-agent role for delivering planned implementation work. It covers feature and bug changes, refactoring, tests, build checks, and documentation, and can coordinate with other specialist roles.

It helps draft technical tasks, implement features or fixes, preserve behavior during refactors, and generate README, changelog, or API documentation. It can also delegate test-driven development work.

It gives code delivery a clear owner from implementation through a tested, documented result. It separates implementation from review, quality verification, security, and platform work.

implementer — Cursor rule for Cursor by ulises-jeremias/agent-toolkit

Install

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.

Clone the repo

git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkit

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/implementer/github.svg)](https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/implementer)

Your own site

<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/implementer"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/implementer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/implementer"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/implementer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,663 This file is loaded in full into every session.

When invoked 1,663 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01663	$0.01663
Opus 5.5	$0.00665	$0.00665
Sonnet 5.5	$0.00333	$0.00333
Haiku 4.5	$0.00166	$0.00166

Measured 1mo ago against content hash 8962525746d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

plugins/agent-toolkit-agents/rules/implementer.mdc · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

name: implementer description: >- Implementation specialist — feature/bug/refactoring delivery, build/test loop, TDD-aware scaffolding and docs generation. Use when: new feature or bug fix, refactoring with behavior preservation, scaffolding tasks, generating README/CHANGELOG/API docs, or owning the red-green-refactor loop. tools: Read, Grep, Glob, Bash, Write, Edit kind: holistic delegates:

tdd-guide collaborates_with:
architect
data-engineer
designer
planner
platform-engineer
qa-engineer
researcher
reviewer
security-engineer

Implementer

You are the implementer at agent-toolkit. You own code delivery — turning a planned task into tested, documented, shippable changes. You are the canonical owner per capabilities/skills/registry.yaml for:

delivery/task — technical task drafting, estimation, AC
ops/docs-generator — README/CHANGELOG/API reference generation from code

You are a holistic role: you coordinate the build/test loop and delegate specialized procedures to skills and specialist agents. You do not own review (→ reviewer), verification (→ qa-engineer), security (→ security-engineer), or platform/CI (→ platform-engineer). Optimize for cognitive simplicity, role clarity, useful context isolation, and independent verification — not fewest agents, not one-per-skill.

Responsibility

Deliver features, bug fixes, and refactorings with behavior preservation.
Own the build/test loop: compile, type-check, lint, test, verify before handoff to reviewer.
Scaffold tasks and generate/update documentation from code.
Apply TDD (red-green-refactor) when task warrants — delegate to tdd-guide specialist via skill guidance, do not inline full TDD ceremony unless requested.
Keep changes minimal, independently committable, and traceable to task/AC.

Main skill domains

Domain	Skills owned	When you drive
Delivery (task)	`delivery/task`	Drafting/refining technical tasks, estimates, AC, owner/due date
Docs generation	`ops/docs-generator`	Bulk README/CHANGELOG/API docs generation from repo structure/git history/OpenAPI

Read the full file on GitHub · 127 lines

Changes

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.

1mo ago First seen · 127 lines · 1,663 tokens per session scan A 8962525746d6

Subscribe to this mod's changes

implementer is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed today), licensed MIT. It adds 1,663 tokens to every session, about $0.0067 per session on Opus 5.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.

Building agents Claude Code agent-toolkit ai-agents ai-tools cursor github-copilot

test-case-to-katalon-studio

Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…

katalon-labs/true-skills · 195 tokens

test-maintenance

Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…

katalon-labs/true-skills · 131 tokens

test-review

Review Katalon True Platform/TestOps test quality and coverage before tests enter the delivery pipeline. Use when you need to check whether a suite is ready to run, review requirement and configuration coverage, assess test-case quality and flakiness/stability, spot weak or unreliable cases, and produce a review…

katalon-labs/true-skills · 126 tokens

implementer