Zeroshot is a software-change orchestration tool that separates implementation from verification: one coding agent makes a change and another independently checks whether it works. Developers use it to run coding tasks in isolated Git worktrees and continue the executor–verifier loop until the result is verified or a concrete failure is reported. The catalogue includes instructions, a hook, a skill, a setting, and a command for Zeroshot.
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 skills add the-open-engine/zeroshot --skill zeroshot-memory-initgit clone --depth 1 https://github.com/the-open-engine/zeroshotWrote 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/skills/the-open-engine/zeroshot/zeroshot-memory-init)<a href="https://agentmods.dev/skills/the-open-engine/zeroshot/zeroshot-memory-init"><img src="https://agentmods.dev/badge/skills/the-open-engine/zeroshot/zeroshot-memory-init/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/the-open-engine/zeroshot/zeroshot-memory-init"><img src="https://agentmods.dev/badge/skills/the-open-engine/zeroshot/zeroshot-memory-init.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.01211 |
| Opus 5.5 | $0.00021 | $0.00484 |
| Sonnet 5.5 | $0.00011 | $0.00242 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
zeroshot-memory-init 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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Zeroshot Active Memory
Use the host agent's subagents and model connections. The CLI exports evidence, validates responses and publishes lessons; it makes no model calls. A session covers all discovered local repositories. Preserve any repository or graph exclusions the user gave. A host without subagent orchestration must report that limitation rather than combine the specialists into one conversation.
Choose a private session directory outside repository checkouts. Call:
zeroshot memory init --directory /path/to/session
The first call creates the private directory; later calls resume it. After each requested set of
agent work finishes, call the same command again. Use the returned phase and next_action to
decide what to do. The invoking folder does not limit history. There is no --cwd flag.
Never use the former memory review or memory commit commands.
Apply user exclusions through optional --ignore-repos and --ignore-graphs lists on the first call.
Values may be comma-separated, space-separated or repeated. Repository aliases include checkout
folder name, absolute path, admitted repository name, forge owner/repo, and opaque namespace, as
reported per run. Graph aliases are exact authored root names or exact hashes; historical admission
does not retain original profile names. Matching is exact and case-sensitive. A short repository name
can exclude several repositories. Saved lists persist when omitted on resume; conflicting lists
require a new session. The skill still classifies every remaining candidate and honors user
exclusions that require inspecting graph contents. Inventory reports missing or changed recorded checkouts as
explicit exclusions; continue with other repositories. If a selected checkout later disappears or
changes repository identity, stop publication and report that it must be restored or excluded in a
new session; never silently drop supplied cards. Never guess a replacement checkout.
Discovery
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.
- 3d ago Changed 9e5311eb473d
- 4d ago First seen · 91 lines · 53 tokens per session scan A 0a2d8e00fe71
zeroshot-memory-init is a skill published in the GitHub repository the-open-engine/zeroshot (2,050 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,211 once invoked, about $0.0002 per session on Opus 5.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-10-24.
Other skills, from other repositories
state-management
STATE.md reading, writing, and field-level updates. Provides cross-session state persistence via .planning/STATE.md with structured fields for current task, completed phases, blockers, decisions, and quick tasks.
mem0-integration
Mem0 memory layer integration for AI agents. Implement persistent, semantic memory for long-term context retention and personalization.
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
persistent-memory
Observation capture and retrieval across sessions. Stores decisions, discoveries, and bugfix patterns. Searchable via tags and relevance scoring.
context-management
Project context loading, isolation, and persistent state management across CCPM sessions.
session-memory
Mandatory memory persistence system across session resets using three markdown surfaces in .claude/cc10x/. Iron law - every workflow must load at start and update at end.