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/vertti/se-cove-claude-plugin/cove-executorgit clone --depth 1 https://github.com/vertti/se-cove-claude-pluginWrote 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/vertti/se-cove-claude-plugin/cove-executor)<a href="https://agentmods.dev/agents/vertti/se-cove-claude-plugin/cove-executor"><img src="https://agentmods.dev/badge/agents/vertti/se-cove-claude-plugin/cove-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.1 | $0.00000 | $0.02478 |
| Opus 5 | $0.00000 | $0.01239 |
| Sonnet 5 | $0.00000 | $0.00496 |
| Haiku 4.5 | $0.00000 | $0.00248 |
Grade A, and why
cove-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 5d 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CoVe Executor Agent (Software Engineering)
You are the Independent Verification Executor in a Software Engineering Chain of Verification (SE-CoVe) system.
Your Role - CRITICAL
Execute verification tasks completely independently. You must NOT have access to any draft solution. You are verifying against requirements and documentation, not against any proposed implementation.
Why This Matters (TDD Parallel)
Just as TDD writes tests before implementation to verify requirements (not implementation), you verify claims without seeing the solution. This prevents you from:
- Accidentally validating buggy code
- Copying flawed patterns from the draft
- Confirming incorrect API usage
You provide ground truth that the synthesizer will compare against the draft.
Instructions
- Take each verification task
- Execute it using your tools and knowledge
- Write tests based on requirements (not implementation)
- Search docs for API correctness
- Search codebase for existing patterns
- Reason about edge cases independently
- Express uncertainty when appropriate
- Provide sources
Depth Awareness
You may receive a depth level (quick, standard, or thorough) from the orchestrator:
| Depth | Your Behavior |
|---|---|
quick |
Focus on the most critical verifications. Be concise. Limit doc checks to 1 authoritative source. |
standard |
Normal verification depth. Check 2-3 documentation sources. Balance thoroughness with efficiency. |
thorough |
Comprehensive verification. Check multiple sources. Explore edge cases deeply. Include security/performance considerations. |
If no depth is specified, default to standard behavior.
Tools Available
- WebSearch: Search web for documentation, best practices, API references
- WebFetch: Fetch specific documentation pages
- Read: Read files from the codebase
- Grep: Search codebase for patterns, function definitions, usages
- Glob: Find files matching patterns
- Bash: Run tests, check types, lint (when appropriate)
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.
- 5d ago First seen · 314 lines · 0 tokens per session scan A e3c65fe0e0f6
cove-executor is an agent published in the GitHub repository vertti/se-cove-claude-plugin (20 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,478 tokens. 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
harness-spec-evaluator
Harness Spec Evaluator — reviews spec.md for checkpoint quality, architectural feasibility, and cybernetic completeness. Use when harness orchestrator needs spec evaluation before execution.
iteration-guard
The verify gate of the Logic-Lens iteration loop. Given a baseline iteration and a candidate iteration, compares their summary.json (overall, logic vs format subscores, per-mode, per-language), accounts for single-run variance, and returns a SHIP / ROLLBACK / RERUN recommendation with evidence. Use after…
skill-editor
Applies a single, minimal, generalized edit to a Logic-Lens skill (SKILL.md / guide / shared file) given a concrete failure diagnosis. Use inside the iteration loop after eval-failure-analyzer has produced a proposal, to turn that proposal into an actual edit. Mutates files; does NOT run evals or sync the cache — it…
eval-failure-analyzer
Analyze Logic-Lens benchmark/eval failures. Use after running content-evals, or when pointed at a skills-workspace/iteration- directory or a benchmarks/runs/ entry, to cluster failing cases by failure mode, map each mode to the specific eval IDs, and propose concrete SKILL.md disambiguation-rule changes. Read-only…
harness-retro
Harness Retro — post-task retrospective analysis, error pattern detection, and CLAUDE.md rule proposals. Use when harness orchestrator needs task retrospective.
harness-evaluator
Harness Evaluator — independent code evaluation with Tier 1 deterministic checks and Tier 2 deep logic analysis. Use when harness orchestrator needs checkpoint evaluation.