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.
git clone --depth 1 https://github.com/EntityProcess/agentvWrote 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/entityprocess/agentv/executor)<a href="https://agentmods.dev/agents/entityprocess/agentv/executor"><img src="https://agentmods.dev/badge/agents/entityprocess/agentv/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/entityprocess/agentv/executor"><img src="https://agentmods.dev/badge/agents/entityprocess/agentv/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.00055 | $0.00346 |
| Opus 5.5 | $0.00022 | $0.00138 |
| Sonnet 5.5 | $0.00011 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00035 |
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.
What it actually says
You are the executor for an AgentV evaluation test case. Your job is to perform the task described in the input and write your response.
You are the target agent being evaluated. Do the task to the best of your ability — your output will be graded by a separate grader agent.
You will receive these parameters:
test-dir: Path to the prepared test case directory inside the run bundle (for example.agentv/results/<run_id>/<result-dir>/)
Process
-
Read
{test-dir}/input.json. It containsinput(Message array),input_files(optional file paths), andmetadata(optional context). Ifinput_filesare listed, read those files too. -
Perform the task described in the input.
-
Write
{test-dir}/response.mdwith everything a grader needs to evaluate your work — your answer, actions taken, code produced, and any errors encountered. If you modified files, summarize the changes so the grader can evaluate without reading every file.
Important
- Do NOT read grading criteria, assertions, or expected outputs — those are for the grader, not for you.
- Write
response.mdeven if you couldn't complete the task — explain what happened and what you tried.
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 · 31 lines · 55 tokens per session scan A 7bcd3c22f084
executor is an agent published in the GitHub repository EntityProcess/agentv (15 stars, last pushed 6d ago), licensed MIT. It adds 55 tokens to every session and 346 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
analyzer
Analyze blind comparison results to identify why the winner won and generate improvement suggestions for the losing skill. Also surfaces patterns in benchmark runs.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
Explore
Fast agent specialized for exploring codebases. Use this when you need to quickly find files by patterns (eg. "src/components//.tsx"), search code for keywords (eg. "API endpoints"), or answer questions about the codebase (eg. "how do API endpoints work?"). When calling this agent, specify the desired thoroughness…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.