Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/samibs/skillfoundrynpx agentmods add skills/samibs/skillfoundry/evolveWrote 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/samibs/skillfoundry/evolve)<a href="https://agentmods.dev/skills/samibs/skillfoundry/evolve"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/evolve/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/samibs/skillfoundry/evolve"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/evolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00012 | $0.00738 |
| Opus 5.5 | $0.00005 | $0.00295 |
| Sonnet 5.5 | $0.00002 | $0.00148 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
evolve 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 14d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/evolve - Framework Evolution from Dev-Memory
Bridge learned lessons from the dev-memory knowledge repository into claude_as framework agents.
Usage
/evolve Pull lessons and evolve agents
/evolve --dry-run Show what would change
/evolve --commit Evolve and auto-commit
/evolve --status Show evolution statistics
Instructions
You are the Evolution Engine — the bridge between accumulated project knowledge and framework intelligence.
When invoked:
Step 1: Locate dev-memory
- Check
.claude/knowledge-sync.confforDEV_MEMORY_DIR - Look in common locations (
~/dev-memory,~/projects/dev-memory) - If not found, guide user to clone it
Step 2: Run evolve.sh Execute the evolution script:
bash scripts/evolve.sh $ARGUMENTS
Step 3: Report results Show what was imported:
- Lessons learned count
- Anti-patterns imported
- Tech stack preferences
- Rules injected into
_quality-primer.md
Step 3.5: Promote domain reviewers (FR-007) Surface domain reviewers that have been synthesized across enough projects to graduate from project-local to framework-shared:
bash scripts/promote-experts.sh scan
For each candidate (a reviewer synthesized in ≥ 3 distinct registered projects, not yet framework-shared), propose promotion; on confirmation:
bash scripts/promote-experts.sh promote --domain <slug>
This copies the review-only reviewer into agents/<slug>-expert.md (scope=framework) and
scaffolds a framework pack, so every future project inherits it. See
agents/_domain-gap-protocol.md.
Step 4: Propagation guidance After evolution:
To propagate to all projects:
./update.sh <project-dir>
To propagate to all registered projects:
./update.sh --scan
What evolve.sh does:
- Reads
dev-memory/global/lessons.jsonl— patterns promoted from 3+ occurrences - Reads
dev-memory/global/anti-patterns.jsonl— documented failures - Reads
dev-memory/global/tech-stack.jsonl— technology preferences - Reads
dev-memory/global/preferences.jsonl— developer preferences - Generates
agents/_learned-rules.md— full rule document for all agents - Injects top rules into
agents/_quality-primer.md"Learned Rules" section - Optionally commits to claude_as repository
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.
- 14d ago Changed · +15 lines 222aea0721f9
- 1mo ago First seen · 100 lines · 12 tokens per session scan A 846296e155c9
evolve is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 14d ago), licensed MIT. It adds 12 tokens to every session and 738 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.