ai-agent-memory: Skill for Claude Code

.claude/skills/new-engagement/SKILL.md

new-engagement is a skill for Claude Code from ozgurkarahan/ai-agent-memory. It costs 58 tokens per session (2,152 once invoked), scanned C, original, MIT.

A project setup helper for starting client engagement projects from a saved template. It reads the client, topics, format, and destination, then prepares the project and its related wiki page.

In plain words
What is it for?
Use it when beginning a new client engagement, such as with “new engagement” or “/new-engagement.” It creates the project folders, fills in AGENT.md, creates a wiki page, and initializes Git.
Why use it?
It removes the repeated manual work of creating folders, copying setup instructions, starting Git, and adding the project to the wiki. It also stops when required template or wiki locations cannot be found.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is ozgurkarahan/ai-agent-memory's own configuration. It tells Claude Code how to work on ai-agent-memory 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 ai-agent-memory configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ozgurkarahan/ai-agent-memory. 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/ozgurkarahan/ai-agent-memory/master/.claude/skills/new-engagement/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ozgurkarahan/ai-agent-memory

Made for: Claude Code.

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 new-engagement

README.md
[![agentmods](https://agentmods.dev/badge/skills/ozgurkarahan/ai-agent-memory/new-engagement/github.svg)](https://agentmods.dev/skills/ozgurkarahan/ai-agent-memory/new-engagement)
Your own site
<a href="https://agentmods.dev/skills/ozgurkarahan/ai-agent-memory/new-engagement"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/ai-agent-memory/new-engagement/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 new-engagement

Your own site · 80×15
<a href="https://agentmods.dev/skills/ozgurkarahan/ai-agent-memory/new-engagement"><img src="https://agentmods.dev/badge/skills/ozgurkarahan/ai-agent-memory/new-engagement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,152 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00058 $0.02152
Opus 5 $0.00029 $0.01076
Sonnet 5 $0.00012 $0.00430
Haiku 4.5 $0.00006 $0.00215

Measured 11d ago against content hash 845881d72e77, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade C, and why

new-engagement scanned grade C with 1 finding 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 11d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$PROJECT_DIR/.git"
.claude/skills/new-engagement/SKILL.md · 249 lines

How it starts

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

New Engagement

When the user says "new engagement", "scaffold engagement", or invokes a slash command like /new-engagement, scaffold one or more client engagement projects from the resolved project template.

Resolve required roots

Before scaffolding:

  1. Resolve WIKI_ROOT using memory/schema.md, then schema.md, then the memory-wiki path declared in AGENT.md.
  2. Resolve TEMPLATE_ROOT by checking for project-template/ beside WIKI_ROOT, then the path declared in AGENT.md.
  3. If the template is absent but network access is available, the agent may clone https://github.com/ozgurkarahan/ai-agent-memory.git into a temporary folder and use its project-template/ directory.
  4. If either root remains unresolved, report the missing root and stop. Do not guess a personal path.
  5. Remove any temporary clone after scaffolding.

All wiki paths below are relative to WIKI_ROOT.

Step 1: Parse the request

Extract from the user input:

  • Client name (e.g., "Acme", "Contoso", "Contoso")
  • Topics — one or more engagement topics, each with a format
  • Projects root — use an explicit destination from the request or AGENT.md; otherwise ask where to create the client workspace

Expected input format: <ClientName> — <topic1> (format), <topic2> (format)

Formats: presentation, workshop, demo, presentation + demo, or combinations.

If the input is ambiguous or missing details, ask clarifying questions:

  • What is the target audience? (e.g., technical leadership, developers, executives)
  • What format? (presentation, workshop, demo, or combination)
  • What are the key objectives?
  • Any specific technologies or topics to cover?

Step 2: Scaffold each project

For each topic, do the following.

2a. Create project directory

PROJECT_DIR={PROJECTS_ROOT}/{ClientName}/10-projects/{project-slug}
mkdir -p "$PROJECT_DIR"

Convert the topic to a kebab-case slug (e.g., "Agent Framework Engagement" → agent-framework-engagement).

Read the full file on GitHub · 249 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. 11d ago First seen · 249 lines · 58 tokens per session scan C 845881d72e77

Subscribe to this mod's changes

new-engagement is a skill published in the GitHub repository ozgurkarahan/ai-agent-memory (8 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 2,152 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens