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 commands/wake-engineering/ai-plugin/publish-copygit clone --depth 1 https://github.com/wake-engineering/ai-pluginWhat 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 | $0.00069 | $0.01205 |
| Opus 5 | $0.00034 | $0.00602 |
| Sonnet 5 | $0.00014 | $0.00241 |
| Haiku 4.5 | $0.00007 | $0.00120 |
Grade A, and why
publish-copy 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish-Copy Command (internal)
Internal tooling. This command lives under
tooling/and is excluded from the marketplace payload. End users never see it.
Canonical Wake API docs: https://wakecommerce.readme.io/docs/schema (for any Wake API references in copied content).
Copy marketplace-ready plugin artifacts from the toolkit repo to the publish repository. Only spec-derived paths are copied; internal tooling (including this command) is excluded.
Prerequisites
-
Read the rule: Load
tooling/rules/publish-copy.mdcfor inclusion and exclusion paths. -
Resolve destination:
- If
.publish-config.jsonexists and hasdestination: use it - Else if
PUBLISH_REPO_PATHenv is set (in shell or read from.env.localvia the safe parser below): use it - Else: prompt user for destination path
Config overrides env if both are set.
- If
Workflow
- Read
tooling/rules/publish-copy.mdc— get inclusion and exclusion lists. - Resolve destination per Prerequisites above.
- Create destination if it does not exist (mkdir -p).
- Copy each inclusion path from repo root to destination:
.cursor-plugin/.claude-plugin/.mcp.jsonskills/agents/commands/README-publish.md(copied asREADME.md— marketplace version without toolkit-only Publish-Copy section)assets/scripts/
- Never copy
tooling/orrules/(the publish-copy command and rule must not ship). - Overwrite existing files at destination.
- Report:
- If nothing to copy (no inclusion paths exist): report and exit
- Otherwise: list copied paths and confirm completion
Execution
Read PUBLISH_REPO_PATH from .env.local with an explicit KEY=VALUE parser. Do NOT source the file — sourcing executes arbitrary shell from a config file and is unsafe.
PowerShell (default on Windows):
if (Test-Path .env.local) {
$line = Select-String -Path .env.local -Pattern '^PUBLISH_REPO_PATH=' | Select-Object -Last 1
if ($line) { $env:PUBLISH_REPO_PATH = ($line.Line -replace '^PUBLISH_REPO_PATH=','').Trim('"',"'") }
}
$dest = $env:PUBLISH_REPO_PATH
if (-not $dest -and (Test-Path .publish-config.json)) {
$dest = (Get-Content .publish-config.json -Raw | ConvertFrom-Json).destination
}
if (-not $dest) { Write-Error "Set PUBLISH_REPO_PATH in .env.local, or create .publish-config.json with destination"; exit 1 }
New-Item -ItemType Directory -Force -Path $dest | Out-Null
foreach ($d in '.cursor-plugin','.claude-plugin','skills','agents','commands','assets','scripts') {
if (Test-Path $d) { Copy-Item -Recurse -Force $d $dest }
}
if (Test-Path .mcp.json) { Copy-Item -Force .mcp.json "$dest\.mcp.json" }
if (Test-Path README-publish.md) { Copy-Item -Force README-publish.md "$dest\README.md" }
Write-Host "Publish-copy complete. Destination: $dest"
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 · 95 lines · 69 tokens per session scan A f6ca86162b25
publish-copy is a command published in the GitHub repository wake-engineering/ai-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 1,205 once invoked, about $0.0003 per session on Opus 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.