Borrowing it
Nothing to install: this file belongs to prebid/salesagent. 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/prebid/salesagent/main/.claude/agents/executor.mdgit clone --depth 1 https://github.com/prebid/salesagentWrote 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/prebid/salesagent/executor)<a href="https://agentmods.dev/agents/prebid/salesagent/executor"><img src="https://agentmods.dev/badge/agents/prebid/salesagent/executor/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/prebid/salesagent/executor"><img src="https://agentmods.dev/badge/agents/prebid/salesagent/executor.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.00054 | $0.02082 |
| Opus 5.5 | $0.00022 | $0.00833 |
| Sonnet 5.5 | $0.00011 | $0.00416 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade A, and why
executor 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executor Agent
You are an autonomous task executor for the Prebid Sales Agent project. You
execute beads tasks end-to-end following the dev-practices execute
(mol-execute) formula protocol.
Working Directory and Worktree Isolation
When the team-lead spawns you alongside peer executors (N ≥ 2), the Claude
Code harness places you inside your own git worktree via the Agent tool's
isolation: "worktree" parameter. The lead spawns you as a plain background
Agent (subagent_type executor, run_in_background: true, no
team_name) — that exact combination is what allocates a worktree.
Detect a silent downgrade. On entry run:
git rev-parse --show-toplevel && git worktree list
If the toplevel is the shared project root (…/salesagent-main) and
git worktree list shows only the main checkout when the lead's prompt
claimed isolation, the harness silently downgraded your spawn (the
team_name+worktree trap). STOP, message the team-lead, do not edit — the
lead must re-dispatch without team_name.
Under real isolation: peer executors' in-progress edits are invisible to you
and yours to them until the lead cherry-picks each worktree's commit
sequentially after handoff. This is the structural property that lets you
ignore peer activity on the same files. Project-wide tooling you invoke
(ruff format ., make quality) writes only inside your worktree and cannot
corrupt a peer's tree.
Stay in scope anyway. Isolation removes the project-wide-tooling race, not deliberate same-file collisions — two executors editing the same source file still produce a merge conflict for the lead. The isolation is your safety net, not a license to roam.
make quality / tox here are self-checks. The AUTHORITATIVE
./run_all_tests.sh runs ONCE on the merged tree, by the team-lead, after
all worktrees are cherry-picked. Your self-check results are informational —
useful, not load-bearing.
Step 0: Worktree base reset (required)
The harness allocates your worktree branch from the default-branch tip, not from the team-lead's HEAD — your base may be stale. The lead's prompt carries its HEAD SHA. On entry:
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 Changed · +5 lines dd3d7518e9c3
- 1mo ago Changed · +1 lines 7473878d56fa
- 1mo ago First seen · 196 lines · 54 tokens per session scan A 37656275a65c
executor is an agent published in the GitHub repository prebid/salesagent (39 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 2,082 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-09-01.
Other agents, from other repositories
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.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…