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 skills/cwinvestments/memstack/forgenpx skills add cwinvestments/memstack --skill forgegit clone --depth 1 https://github.com/cwinvestments/memstackWhat 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.00029 | $0.00524 |
| Opus 5 | $0.00015 | $0.00262 |
| Sonnet 5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
forge 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.
What it actually says
🔨 Forge — Creating New Enchantment...
Create new MemStack skills or improve existing ones.
Activation
When this skill activates, output:
🔨 Forge — Creating new enchantment...
Then execute the protocol below.
Protocol
Creating a new skill:
-
Ask the user:
- What should the skill do?
- What trigger keywords should activate it?
- What inputs does it need? What should it output?
-
Generate the skill file with v2.1 format:
- YAML frontmatter with name and description ("MUST use when..." format)
- Activation message (pick an appropriate emoji)
- Context guard (if the skill could have false positives)
- Protocol steps
- Inputs/Outputs
- Example usage
- Level history starting at Lv.1
-
Write the file to
$MEMSTACK_PATH/skills/{name}.md -
Update MEMSTACK.md — add a new row to the Skill Index table
-
Confirm creation — show the skill summary
Improving an existing skill:
- Read the current skill file
- Apply improvements based on user feedback
- Increment the level in Level History
- Update the file
Inputs
- Skill concept description, trigger keywords, desired behavior
Outputs
- New skill .md file in skills/
- Updated MEMSTACK.md index
Example Usage
User: "forge a new skill called Beacon for health check pinging"
🔨 Forge — Creating new enchantment...
Creating: Beacon
Emoji: 🔔 | Type: Passive | Triggers: "health check", "ping", "uptime"
Writing: skills/beacon.md ✓
Updating: MEMSTACK.md — added row #N ✓
Beacon is ready. Triggers: "health check", "ping", "uptime"
Level History
- Lv.1 — Base: Skill file generation and index updates. (Origin: MemStack v1.0, Feb 2026)
- Lv.2 — Enhanced: Added YAML frontmatter, v2.1 format generation, level tracking. (Origin: MemStack v2.0 MemoryCore merge, Feb 2026)
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 · 77 lines · 29 tokens per session scan A fa07e0cd5e27
forge is a skill published in the GitHub repository cwinvestments/memstack (417 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 524 once invoked, about $0.0001 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-30.
Other skills, from other repositories
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively…