memoria: Instructions file for Kiro

.kiro/steering/goal-driven-evolution.md

memoria goal-driven-evolution.md is an instructions file for Kiro from matrixorigin/memoria. It costs 1,375 tokens per session, scanned A, original, Apache-2.0.

Instructions for combining persistent memory with goals and plans. They describe how to register a goal, record a multi-step plan, track progress, and save feedback for later work.

In plain words
What is it for?
Use it for projects that span several steps or sessions, including checking earlier goals, recording plans, marking completed steps, and capturing user corrections.
Why use it?
They prevent multi-step tasks from losing their objective, plan, or lessons between conversations. They also encourage continuing an existing goal instead of creating a duplicate.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is matrixorigin/memoria's own configuration. It tells Kiro how to work on memoria itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything memoria configures →

Reuse

Borrowing it

Nothing to install: this file belongs to matrixorigin/memoria. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/matrixorigin/memoria/main/.kiro/steering/goal-driven-evolution.md
Clone the repo
git clone --depth 1 https://github.com/matrixorigin/memoria

Made for: Kiro.

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

agentmods badge for memoria goal-driven-evolution.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/matrixorigin/memoria/goal-driven-evolution/github.svg)](https://agentmods.dev/instructions/matrixorigin/memoria/goal-driven-evolution)
Your own site
<a href="https://agentmods.dev/instructions/matrixorigin/memoria/goal-driven-evolution"><img src="https://agentmods.dev/badge/instructions/matrixorigin/memoria/goal-driven-evolution/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.

agentmods 80×15 button for memoria goal-driven-evolution.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/matrixorigin/memoria/goal-driven-evolution"><img src="https://agentmods.dev/badge/instructions/matrixorigin/memoria/goal-driven-evolution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,375 This file is loaded in full into every session.
When invoked 1,375 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.1 $0.01375 $0.01375
Opus 5 $0.00687 $0.00687
Sonnet 5 $0.00275 $0.00275
Haiku 4.5 $0.00137 $0.00137

Measured 4d ago against content hash 835ecdec5e95, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-13, from the pricing page.

Security

Grade A, and why

memoria goal-driven-evolution.md 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 4d 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.

.kiro/steering/goal-driven-evolution.md · 143 lines

How it starts

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

Goal-Driven Evolution + Plan Integration

Track goals, plans, progress, lessons, and user feedback across conversations. Integrates with plan panels (Kiro Shift+Tab, Cursor Composer, Claude multi-step).

Before Starting Any Multi-Step Task

Query memory first:

memory_search(query="GOAL [topic]")                    # existing related goals
memory_search(query="LESSON [topic]")                  # past learnings
memory_search(query="CORRECTION ANTIPATTERN [topic]") # what NOT to do

If an active goal exists, continue it instead of creating a new one.

Register Goal

For multi-session work (skip for trivial single-session tasks < 3 steps):

memory_search(query="GOAL [keywords]")
memory_store(
  content="🎯 GOAL: [description]\nSuccess Criteria: [measurable]\nStatus: ACTIVE\nCreated: [date]",
  memory_type="procedural"
)

Plan & Execute

Store the plan, then track each step:

memory_store(content="📋 PLAN for GOAL [name]\nSteps:\n1. [step] — ⏳\nRisks: [risks]\nIteration: #1", memory_type="procedural")

# After each step — use working type (will be cleaned up later)
memory_store(content="✅ STEP [N/total] for GOAL [name] (#X)\nAction: [done]\nResult: [outcome]\nInsight: [learned]", memory_type="working")
memory_store(content="❌ STEP [N/total] for GOAL [name] (#X)\nAction: [tried]\nError: [wrong]\nRoot Cause: [why]\nNext: [adjust]", memory_type="working")

Only store non-obvious insights. Don't store "ran tests, passed".

For high-risk iterations, isolate on a branch:

memory_branch(name="goal_[name]_iter_[N]")
memory_checkout(name="goal_[name]_iter_[N]")
# work on branch... then validate and merge (see Iteration Review)

Capture User Feedback (immediately)

User corrections are highest-value — always store as procedural:

# User corrects direction
memory_store(content="🔧 CORRECTION for GOAL [name]: [old approach] → [corrected approach]. Reason: [why]", memory_type="procedural")

# User confirms something works well
memory_store(content="👍 FEEDBACK for GOAL [name]: [what worked]. Reuse: [when to apply again]", memory_type="procedural")

# User is frustrated — record what NOT to do
memory_store(content="⚠️ ANTIPATTERN for GOAL [name]: [what went wrong]. Rule: NEVER [this] again.", memory_type="procedural")

# User changes direction entirely
memory_correct(query="GOAL: [name]", new_content="🎯 GOAL: [name]\n...\nPivot: [old] → [new]. Reason: [why]", reason="User changed direction")

Read the full file on GitHub · 143 lines

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. 4d ago First seen · 143 lines · 1,375 tokens per session scan A 835ecdec5e95

Subscribe to this mod's changes

memoria goal-driven-evolution.md is an instructions file published in the GitHub repository matrixorigin/memoria (596 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,375 tokens to every session, about $0.0069 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-09-08.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,126 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens