publish

A publishing tool that sends private guidelines from the local evolve store to a configured write-scope repository, meaning a repository allowed to receive changes.

In plain words
What is it for?
Use it to publish one or more local guideline files when a write-scope repository is configured.
Why use it?
It makes selected guidelines available to others and records their owner, visibility, publication time, and source while committing and pushing the changes.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/agenttoolkit/altk-evolve/publish
Any agent
npx skills add AgentToolkit/altk-evolve --skill publish
Clone the repo
git clone --depth 1 https://github.com/AgentToolkit/altk-evolve

Made for: Claude Code, Codex.

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,370 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.01370
Opus 5 $0.00007 $0.00685
Sonnet 5 $0.00003 $0.00274
Haiku 4.5 $0.00001 $0.00137

Measured 2d ago against content hash e5e8dca0a791, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

publish 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/publish.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

97% identical to evolve-lite:publish — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

platform-integrations/claude/plugins/evolve-lite/skills/evolve-lite/publish/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Publish a Guideline

Overview

Publish one or more private guidelines from .evolve/entities/guideline/ into a configured write-scope repo. The entity is stamped with visibility: public, owner, published_at, and source, moved into the local clone of the write repo, and committed / pushed to the remote.

The same local clone is also what /evolve-lite:sync pulls from — so you and anyone else publishing to the same repo stay in sync.

Workflow

Step 1: Require a write-scope repo

Read evolve.config.yaml. If no entry has scope: write, tell the user:

"You need at least one write-scope repo to publish to. Run /evolve-lite:subscribe with --scope write to set one up, then come back."

Then stop.

If identity.user is missing, ask for it and add it to the config.

Step 2: First-time setup

Ensure .evolve/ is gitignored at the project root:

grep -qxF '.evolve/' .gitignore 2>/dev/null || echo '.evolve/' >> .gitignore

Step 3: Pick the target write-scope repo

Filter repos: to entries with scope: write (Step 1 already aborted if there were zero, so at least one exists here).

  • Exactly one entry → use it as default.
  • Multiple entries → show a numbered list with notes and ask which to publish to.

Let {repo} be the chosen repo name and {branch} its configured branch (default main).

Step 4: List and select entities

List files in .evolve/entities/guideline/ and ask the user which to publish.

Step 5: Run publish script

For each selected file, run:

python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/publish/scripts/publish.py \
  --entity "{filename}" \
  --repo "{repo}" \
  --user "{identity.user}"

Step 6: Commit and push

Build {names} as a comma-joined list of selected filenames, and {guideline_paths} as a space-joined list of the corresponding guideline/{filename} paths inside the clone (the files the publish script just wrote).

git -C ".evolve/entities/subscribed/{repo}" add -- {guideline_paths}
git -C ".evolve/entities/subscribed/{repo}" commit -m "[evolve] publish: {names}"
git -C ".evolve/entities/subscribed/{repo}" push origin "{branch}"

Read the full file on GitHub · 146 lines

Files

What ships with it

1 file beside SKILL.md 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.

Changes

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.

  1. 2d ago First seen · 146 lines · 14 tokens per session scan A e5e8dca0a791

Subscribe to this mod's changes

publish is a skill published in the GitHub repository AgentToolkit/altk-evolve (105 stars, last pushed 7d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,370 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to evolve-lite:publish, differing in 13 lines, and is treated as a copy.