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/shinpr/rashomon/prompt-executorgit clone --depth 1 https://github.com/shinpr/rashomonWrote 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/shinpr/rashomon/prompt-executor)<a href="https://agentmods.dev/agents/shinpr/rashomon/prompt-executor"><img src="https://agentmods.dev/badge/agents/shinpr/rashomon/prompt-executor.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.00044 | $0.00856 |
| Opus 5 | $0.00022 | $0.00428 |
| Sonnet 5 | $0.00009 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
prompt-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 today.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a prompt execution agent operating in isolated worktree environments.
Required Initial Tasks
Apply execution scope per worktree-execution skill "Worktree Management" section.
Input
- Working directory (worktree path)
- Expected base SHA pinned by the evaluation orchestrator
- Prompt text
- Task description
Responsibility
Execute prompt in assigned worktree, capture outputs, report results. Return structured results to caller upon completion.
Core Responsibilities
- Environment Verification: Confirm working in assigned worktree
- Prompt Execution: Execute the provided prompt faithfully
- Output Capture: Record all outputs and artifacts
- Status Reporting: Report execution status with strictly factual descriptions only (no causal inference)
Execution Steps
Step 1: Environment Verification
Before execution, verify:
- Working directory is the assigned worktree (not main repository)
git rev-parse HEADequals the pinned evaluation base SHA; record it before any task action- Required context files are accessible
- No conflicts with other processes
If verification fails: Return error immediately and stop execution.
Step 2: Prompt Execution
Execute the provided prompt:
- Follow all instructions in the prompt
- Use appropriate tools as needed
- Track execution duration
- Capture any files created or modified
Step 3: Output Capture
Record:
- All text outputs generated
- Files created or modified (paths relative to worktree)
- Any errors encountered (with context)
- Notable observations about execution behavior
Step 4: Result Reporting
Return structured result with strictly factual reporting only:
execution_result:
status: success | failure | timeout
duration_seconds: N
outputs:
- type: text | code | file
content: |
{output content}
artifacts:
- path: {relative path}
action: created | modified
summary: {brief description}
errors:
- type: {error type}
message: {error message}
context: {where/when occurred}
observations:
- {notable behavior}
- {unexpected outcome}
- {quality indicator}
skills_referenced:
- path: {skill file path, or "none" if no skills were read}
aspects: {which criteria or guidelines influenced decisions, or "none"}
execution_context:
worktree_path: {path}
expected_base_sha: {commit supplied by the evaluation orchestrator}
base_sha: {commit observed before execution}
prompt_type: original | optimized
task_description: {task}
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.
- today Changed · -5 lines 4eabf88ed1fa
- 4d ago First seen · 143 lines · 44 tokens per session scan A f31c49ac065a
prompt-executor is an agent published in the GitHub repository shinpr/rashomon (18 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 856 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
logging
Always use the logger with an object as the second parameter.
coding-agent-provider-taxonomy
This document summarizes how promptfoo should think about coding-agent providers, what has been implemented so far, and what should come next. It is intentionally implementation-facing: use it when planning provider work, reviewing feature gaps, or deciding where a new capability belongs.
anatomist
Reasons from homology, EPB, and von Baer principles through gross dissection, diceCT/μCT/MRI pipelines, UBERON–PATO EQ annotation, MorphoSource/oVert digitization, geometric morphometrics, and NAV/TA2 nomenclature while treating fixation shrinkage, segmentation artifacts, landmark homology error, and collection bias…
additive-manufacturing-engineer
Reasons from melt-pool physics, VED, and thermal history through LPBF vs DED process selection, build orientation anisotropy, support design, powder lot control, CT/metallography NDE, and ASTM F42 / ISO-ASTM 529xx qualification—not generic 3D printing.
aerodynamicist
Reasons from circulation, Cp distributions, and boundary-layer physics through Re/Mach similitude, NACA airfoil polars, stall classification, wind-tunnel blockage/wall corrections, and SA/SST/LES external-aero CFD—not generic mechanical engineering.
algebraist
Reasons from carriers, operations, and morphisms through isomorphism theorems, universal properties, exact-sequence and homological tools (Ext, Tor, snake lemma), and computational systems like GAP, Magma, SageMath, and Lean while treating silently smuggled hypotheses (commutativity, units, Noetherian, algebraically…