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.
git clone --depth 1 https://github.com/backchainai/backchain-pluginsWrote 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/commands/backchainai/backchain-plugins/promote)<a href="https://agentmods.dev/commands/backchainai/backchain-plugins/promote"><img src="https://agentmods.dev/badge/commands/backchainai/backchain-plugins/promote/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/commands/backchainai/backchain-plugins/promote"><img src="https://agentmods.dev/badge/commands/backchainai/backchain-plugins/promote.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.00000 | $0.00867 |
| Opus 5.5 | $0.00000 | $0.00347 |
| Sonnet 5.5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
promote 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: promote
Move .memory/ artifacts to permanent knowledge locations.
Trigger
/engram:working promote or natural language: "promote working memory", "move memory to permanent".
Behavior
- Verify
.memory/exists in the current directory. - Read all
.memory/files (todos.md,decisions.md,questions.md). - Analyze each artifact and prompt the user to confirm the promotion target. Do not assume a specific tool.
- Present the full plan for review.
- Execute approved promotions.
- Report results.
Promotion analysis
Decisions → ADRs or auto memory
For each decision in decisions.md, classify by significance:
ADR-worthy (significant architectural / design choice):
- Detect a likely ADR location (
docs/adr/if present). Otherwise ask the user where ADRs live in this project. - Determine the next ADR number by scanning existing ADRs.
- Format using the project's ADR template if one exists, otherwise a standard one (context, decision, rationale, consequences).
Auto-memory-worthy (project context worth remembering, but too small for an ADR):
- Write to a new file in the auto-memory directory (
~/.claude/projects/<project>/memory/). - Use the auto-memory frontmatter format (
name,description,type: project). - Add a one-line pointer in
MEMORY.mdif the user has set up an index — confirm with the user before modifying it.
Skip trivial decisions (tool version choices, formatting preferences). Auto memory captures these organically; promoting them is noise.
Todos → issues
For each incomplete todo in todos.md:
- Detect the user's issue tracker from project signals. If undetected or ambiguous, ask once for the session: "Which issue tracker should I use? (Beads, Linear, GitHub Issues, other)"
- Suggest issue type, priority, and labels based on the todo content. Confirm before creating.
- Create the issue using the tool's standard CLI or API.
Skip:
- Completed todos (already done).
- Trivial items (handle inline).
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.
- 1mo ago First seen · 102 lines · 0 tokens per session scan A 328fdfd43a8d
promote is a command published in the GitHub repository backchainai/backchain-plugins (4 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 867 tokens. 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
evolve-lite-adapt-memory
Mirror a just-saved native memory into the shared evolve store so it becomes shareable and auditable.
memory-graph
Open the memory graph visualization in your browser.
f5-ctx
Context and session management - save, restore, optimize.
remembrall-help
List all Remembrall commands, skills, and config options.
f5-context
This command has been consolidated into /f5-ctx.
budget
View context budget allocation — code vs conversation vs memory breakdown.