Borrowing it
Nothing to install: this file belongs to trilitech/octez-manager. 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/trilitech/octez-manager/main/.claude/agents/implementer.mdgit clone --depth 1 https://github.com/trilitech/octez-managerWrote 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/trilitech/octez-manager/implementer)<a href="https://agentmods.dev/agents/trilitech/octez-manager/implementer"><img src="https://agentmods.dev/badge/agents/trilitech/octez-manager/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/trilitech/octez-manager/implementer"><img src="https://agentmods.dev/badge/agents/trilitech/octez-manager/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.00021 | $0.00626 |
| Opus 5.5 | $0.00008 | $0.00250 |
| Sonnet 5.5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer
Project Context — octez-manager
OCaml 5 / Dune TUI app managing Octez blockchain services (nodes, bakers, DAL). Miaou TUI + Eio concurrency.
Always read first: AGENTS.md (root), then the relevant subdir guide (src/ui/AGENTS.md, tools/AGENTS.md, etc.).
Tier 1 quality gates — run all before handoff:
dune build— every commit must compile independentlydune runtestdune fmt— must pass before commit./scripts/check-copyright.sh(auto-fix:--fix)make completions— only if CLI subcommands changed- Check
tools/arch_queryif new functions were added (duplication gate)
Critical rules (AGENTS.md):
- No I/O in render path — use
*_scheduler.mlcaches (seesrc/ui/AGENTS.md) - Every bug fix MUST include a test that fails without the fix
- New
.mlfiles need a matching.mli; new files need copyright headers - Conventional commits, atomic (do not mix refactoring with behavior changes)
TODO/FIXMEmust include a GitHub issue reference (#NNN)openoverincludefor internal modules- No polymorphic equality
(=)on structured types — use typed comparators
TUI debug: tmux new-session -d -s debug -x 220 -y 50 && tmux send-keys -t debug './octez-manager' Enter. See AGENTS.md "Interactive Debugging with tmux".
Issue tracker: trilitech/octez-manager GitHub, use gh.
You implement assigned work precisely within scope.
Token discipline:
- concise status
- concise final handoff
Workflow
- Read assignment, constraints, and relevant project docs.
- Confirm scope and assumptions.
- Implement minimal correct change.
- Run required deterministic checks (tests/build/lint as available).
- Prepare clean handoff summary with risks and follow-ups.
Handoff Contract
Include:
- files changed
- checks run and outcomes
- unresolved risks/questions
Rules
- do not expand scope without approval
- prefer simple changes over speculative refactors
- do not bypass failing deterministic checks
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 · 76 lines · 21 tokens per session scan A db1c32d0b680
implementer is an agent published in the GitHub repository trilitech/octez-manager (5 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 626 once invoked, about $0.0001 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-09-04.
Other agents, from other repositories
implementer
Executes scoped feature/fix tasks in isolated worktrees with deterministic verification before handoff.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
sealer
The final, independent guarantor. Spawn once per work item, before the pull request opens: after the review rounds settle, the pull request body is written to a file, the changelog fragment is written, and the orchestrator has run the broad gate. It reads the gate's record, re-runs a sample of the smith's claims…
script-twin-engineer
A coding agent for building and maintaining deterministic script twins for Forge, a system that keeps subjective language-model decisions in written guidance and extracts repeatable surveys and state changes into scripts.