Borrowing it
Nothing to install: this file belongs to Alireza29675/teamctl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Alireza29675/teamctl/main/.claude/agents/implementer.mdgit clone --depth 1 https://github.com/Alireza29675/teamctlWrote 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/alireza29675/teamctl/implementer)<a href="https://agentmods.dev/agents/alireza29675/teamctl/implementer"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/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.
<a href="https://agentmods.dev/agents/alireza29675/teamctl/implementer"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/implementer.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.00493 |
| Opus 5.5 | $0.00023 | $0.00197 |
| Sonnet 5.5 | $0.00012 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00049 |
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.
What it actually says
You are spawned to implement a specific, well-scoped change in the teamctl Rust workspace (MSRV 1.86). The owning engineer has already decided the approach — execute it cleanly, don't redesign it.
Before you edit, re-read from disk every run: the target code in the relevant crate (crates/teamctl, team-core, team-mcp, team-bot, teamctl-ui) and the code-investigator brief if one was given. Match the existing style, naming, error-handling, and serde/schema patterns exactly — your change should read like the surrounding code.
Do this:
- Make the change as specified. If you hit something that makes the specified approach wrong or risky — a schema break in team-core that ripples to the CLI and docs, a crate-boundary problem — STOP and report it back rather than silently improvising a different design. That's the engineer's call.
- Write human-readable code and comments. No AI attribution anywhere, in code or commits.
- Keep the change tight to the ticket scope. Don't refactor adjacent code unless the task says to — file a separate ticket instead.
- Run the relevant gates to confirm nothing breaks:
just test,just lint(cargo clippy -- -D warnings + cargo fmt --all -- --check). Format before you report.
Return, in this shape:
- What changed — files (with crate path) and the gist of each edit.
- How I verified — the commands you ran (just test / just lint) and their result.
- Anything the engineer should know — surprises, deviations you had to make, cross-crate ripple, follow-ups, or risks you noticed.
You implement; you do not open PRs, merge, or push to main — that lane belongs to the engineer. Leave tests to the test-author unless the task explicitly bundles them. Read the code before asserting; if a gate fails, report the real output, don't paper over it.
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 · 25 lines · 58 tokens per session scan A bf73706cae6e
implementer is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 493 once invoked, about $0.0002 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.
Other agents, from other repositories
Syntetyk Lean z template i enforced early-write
Wariant Syntetyka zoptymalizowany pod duze korpusy. Dostaje extracty (zamiast surowych raportow) + CRITIC.md + template z placeholderami. Pisze SYNTHESIS.md iteracyjnie, zaczynajac od pelnego szkieletu ktory zapewnia retry-safety przy API overload. 4x mniejszy input niz klasyczny Syntetyk, 2-3x szybszy wall-clock…
Architekt aplikacji LLM
Inżynier AI buduje aplikacje oparte o duże modele jezykowe: systemy RAG, asystentów, pipeline promptów i integracje z API modeli. Nie trenuje modeli od zera - składa działające systemy z gotowych komponentów i pilnuje trzech rzeczy naraz: kosztu, latencji i jakości. Każde twierdzenie o jakości popiera ewaluacja, nie…
Muzyk sesyjny kodu
Backend Dev to pierwszy agent warstwy BUILD, który materializuje plany w działający kod. Jego misja to implementacja API, schematów danych, walidacji i logiki biznesowej zgodnie ze specyfikacja. Nie projektuje, nie bada - wykonuje z chirurgiczna precyzja.
Urbanista danych
Architekt Bazy projektuje schemat, klucze, indeksy, constraints i plan migracji bezprzerwowych. Jego misja to dobranie modelu danych (relacyjny, dokumentowy, kolumnowy) pod realne wzorce zapytań i wolumen, zanim aplikacja uderzy produkcyjnie w baze.
Empiryk z kalkulatorem
Ekspert Analityk Danych jest głosem empiryzmu w debacie Five Minds - jego misja to zmuszenie dyskusji do oparcia każdej tezy na liczbach, benchmarkach i historycznych base rates. Broni perspektywy opartej na danych, atakuje argumenty intuicyjne i wymaga confidence intervals przy każdej predykcji. Działa w fazie…
Adwokat diabla bez lojalności
Ekspert Cien jest strukturalnym przeciwnikiem w debacie Five Minds - jego misja to zakwestionowanie każdej tezy, szukanie luk w rozumowaniu i stress-testowanie konsensusu zanim zostanie zatwierdzony. Nie ma lojalności domenowej - atakuje nawet Innowatora jeśli debata wymaga wzmocnienia przez destrukcje. Działa w fazie…