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.
/plugin marketplace add raphaelchristi/harness-evolvernpx agentmods add plugins/raphaelchristi/harness-evolver/marketplacegit clone --depth 1 https://github.com/raphaelchristi/harness-evolverGrade A, and why
harness-evolver-marketplace 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 2d 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
{
"name": "harness-evolver-marketplace",
"owner": {
"name": "Raphael Valdetaro"
},
"metadata": {
"description": "LangSmith-native autonomous agent optimization plugin"
},
"plugins": [
{
"name": "harness-evolver",
"source": "./",
"description": "Evolves LLM agent code using multi-agent proposers, LangSmith experiments, and git worktrees",
"version": "6.1.0",
"author": {
"name": "Raphael Valdetaro"
},
"homepage": "https://github.com/raphaelchristi/harness-evolver",
"repository": "https://github.com/raphaelchristi/harness-evolver",
"license": "MIT",
"keywords": ["langsmith", "optimization", "evolution", "llm", "agent"],
"category": "development"
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 26 lines scan A 894af21166aa
harness-evolver-marketplace is a plugin published in the GitHub repository raphaelchristi/harness-evolver (49 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
better-harness
Build an AI-ready engineering system for safe coding-agent delivery and continuous software improvement.
claude
Connect Claude Code to your local OpenLoomi runtime. One-command install, mirror Claude's lifecycle onto the Loomi Pet, and auto-archive every Stop into your OpenLoomi memory. Talks to your local OpenLoomi over HTTP and the OpenLoomi helper CLI. AI provider config is owned by OpenLoomi itself — this plugin never reads.
heliohq
Helio plugin registry.
workflow
Developer-workflow commands and skills — sandbox-safe Conventional commits with a commit.sh handoff, immutable code-scanning triage reports with SHA-pinned permalinks, and generation of evolve evaluation suites (triggers + behavioral evals) for agent skills.
terraform
Terraform style conventions, module scaffolding, and fmt/validate/tflint workflows for authoring reusable modules.
ratchet
Torque Loop turns ambiguous work into shipped artifacts through target locking, adversarial validation, patching, and state serialization — plus a bounded /ratchet:evolve loop. A stateful advancement engine, not a prompt library. Not affiliated with Anthropic.