Releases: beyond10x/agentplugins
Release list
Agent Plugins 0.9.1
Agent Plugins 0.9.1
- Pin ESS
0.22.1instead of0.20.0. ESS0.22.0had no archives because its own release gate
was red at the tag;0.22.1is the release cut with that gate green and itsReleaserun
publishing the four archives andSHA256SUMS. The install page, the README and the expected
ess --versionline follow. - The ESS skill's example is re-validated on ESS
0.22.1— the same line,warehouse v1 — 2 file(s), valid, exit 0 — and its--pathparagraph no longer has to distinguish the pinned
release fromess-inputs.yaml, which the pinned release reads. - Align the golden path's model-driving command with Metaharness and label its older recorded
CLI output separately from current installation requirements. - Unlike
0.9.0, this release rantask checkandtask site-buildon the tagged tree.
Agent Plugins 0.9.0
- Align installation guidance on AEP
0.55.0and ESS0.20.0, both with published native
archives. Keep ESS0.22.0out of the download instructions while its archives are unavailable. - Use Metaharness
0.7.0for governed model runs throughmetaharness aep drive. Supply the
separate planning executable with--aep-binary, preserve plugin and budget inputs, and
require the explicitMETAHARNESS_LIVE=1opt-in. - Bring the planning skill's command inventory up to AEP
0.55.0, includingwaves,findings,
review-value,setandscope. Explain conformance report ingestion through
evidence --from, report/2 suite binding, model digests and specification lifecycle states. - Document ESS conformance synthesis, execution and evidence ingestion. Distinguish the pinned
ESS0.20.0system-file layout fromess-inputs.yaml, introduced in0.21.0. - Update example crate paths for AEP's area-based layout and keep both plugin manifests and
current installation pins aligned at0.9.0. - Publish source through standalone bot tooling without an Atlas checkout or organization
admission requirement. Repository correctness and release checks remain repository-owned.
Historical walkthrough and paid-evaluation pins remain attached to their original recordings.
This source release was cut without running gates, tests, live evaluations or binary packaging,
at the operator's request. Earlier preparation evidence remains in the planning record.
Agent Plugins 0.8.1
Agentplugins 0.8.1 updates Workspace Hygiene, AEP waves and Connectors for Codex and Claude Code.
- Workspace Hygiene is generated from Worktree 0.4.0 and covers native inspection, explicit leases, release before finish, disposable storage cleanup and owned handoffs.
- AEP waves use managed creation and reviewed GC, with separate coordinator, implementor and adversary leases. Cleanup preserves evidence and only deletes branches recorded for that wave.
- Connectors guidance targets released CLI 0.7.1, with explicit local/hosted targets, exact operation protocols, bounded daemon-free calls, pagination and CLI/daemon upgrade checks.
- Current installation instructions are pinned to Agentplugins 0.8.1 and Worktree 0.4.0.
All six plugin manifests share the release version. Repository, skill/plugin validation and the documentation build passed. Reload the host's plugins or start a new Codex thread after updating the marketplace release pin.
Agent Plugins 0.8.0
-
Fix Connector readiness evaluation for Claude
Bash/commandand Codex
exec_command/cmdtraces. A shared Rust command checker runs alongside AEP's session checks
in replay and live CI; parsed help commands no longer count as mutations. Regression cases
reject real mutations, missing doctor evidence, and mutations chained after help. -
Publish the connectors plugin in the release-pinned installation guides for both hosts.
-
Repair YAML quoting in the ESS skill description so every released plugin validates.
-
Add the focused
connectorsplugin to both marketplaces, with one shared skill for the
Connectors 0.6.0 CLI, secret-safe onboarding, readiness diagnostics, and governed operation
invocation. Include host installation guidance and a readiness eval case. -
The planning skill says how to take an edge back. AEP 0.53.0 adds
aep plan artifact unrelate <id> <relation> <target>, and the skill now names it in the write-verb
list, in guardrail 2, in the mutation-ownership table and in the renaming paragraph. Until this
landed the skill described a store where a relation could be added and never removed, so a session
that made a backwardsblocksedge had nowhere to put the correction but the artifact's body —
which is what a recorded run did on 2026-09-04. A refusal namingunrelateas an unknown verb now
means the installed CLI predates 0.53.0, and the skill says so. -
Every authored document teaches the grouped CLI spelling. AEP 0.52.0 replaced a flat first
level of twenty-three verbs with four areas plusdoctor, and ESS 0.12.0 replaced twenty with
four;
both keep every flat spelling as a hidden alias with identical stdout, stderr and exit status, so
nothing here was broken and nothing is fixed — what changes is what a skill, a charter, a
reference, a page and an eval case teach a reader to type.was is aep validate resolve inspect evaluate explain describe schema workflowaep govern <verb>aep artifact serve entity audit workspace conformance reverseaep plan <verb>aep eval {matrix,run}aep drive eval {matrix,run}aep trace contract property specification evidenceaep observe <verb>ess validate compile compose inspect graph realization runtimeess specify <verb>ess synthesize project schema build release stack deploymentess generate <verb>ess conform diff impactess verify <verb>ess importess infra importaep drive run|status|resume|transition,aep doctorandess generate --path …are what they
were: those verbs did not move. Theprotocolspelling followsaep's, since they are two names
for one binary. -
The eval corpus's command matchers accept either spelling rather than moving to the grouped
one.'(aep|protocol) artifact +move'is now'(aep|protocol) +(plan +)?artifact +move': the
committed transcript ofgolden-path-end-to-endwas recorded under the flat spelling and a row
that stopped matching it would be a specification describing a run other than the one recorded,
while a row that only matched the flat spelling would reportnever_occurredagainst the next
recording made by an agent reading the migrated skills. Widening witnesses a claim; it does not
widen one. The same holds for thetool.absentrow inadversary-tests-only, where accepting
both spellings is what keeps "noartifactcommand ran" from being satisfiable by typing the
other one. -
agentplugins-checkrefuses a flat spelling in any.md,.yamlor.ymlthis repository
authors, rather than leavingAGENTS.md§ Invariants to a person remembering to grep. Sweeping
the tree found 360 of them across 47 files, five of which were in a file no hand list had — the
paid eval workflow.The sweep exempts four prefixes, each visible in a diff:
exempt why CHANGELOG.mdwhat a command was called changes/a dated record, written on the day .engineering/the planning store, whose only writer is the aepCLI.github/workflows/a program, not a lesson: eval.ymlpinsAEP_VERSION: '0.44.0', so its spelling has to be the surface that version hasRust sources are not swept for the same reason as the last row:
evals.rsspawns
aep eval run --streamagainst whichever binary is onPATH, and that call is a call. -
The install page pins AEP 0.52.0 and ESS 0.13.1, the latest published release of each, and
the versions whose--versionlines it quotes. The grouped spelling the pages now teach exists in
AEP from 0.52.0 and in ESS from 0.12.0; the previous pins (0.51.0 and 0.11.1) have neither.
Agent Plugins 0.7.0
Agent Plugins 0.6.2
Agent Plugins 0.6.1
Agent Plugins 0.6.0
Agent Plugins 0.5.1
agentplugins 0.5.1
Pins the Claude marketplace to plugin bytes containing the verified AEP 0.44.0 and ESS 0.5.1 adopter guidance.
Refreshes the eight-step golden path and its behavioral-eval documentation.