Index of every page on this site: llms.txt
All skills
rohitg00 avatar

/forget

@5c9e2e6
by Rohit Ghumarerohitg00/agentmemory30k stars
2,713
Run it yourself

Delete selected durable memories from agentmemory after showing them and getting explicit confirmation. Use when the user says "forget this", "delete memory", "remove that note", or wants to scrub specific data for privacy.

Use this Skill: https://skilld.dev/gh/rohitg00/agentmemory/forget

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈58 tokens for metadata: the name and description. ≈617 when used: this file. ≈1.4k more on demand in 2 files.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈232 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

The user wants to remove data from agentmemory: $ARGUMENTS

Quick start

memory_smart_search { "query": "old api key in config", "targetLayer": "memory", "limit": 20 }

Show the matches, get a yes, then:

memory_governance_delete { "memoryIds": "abc12345,def67890", "reason": "user privacy request" }

Expected output:

Found 2 matching memories. Confirmed. Deleted 2 memories.

Why

This is destructive and irreversible. Show exactly what will be deleted and get an explicit yes before calling delete. Delete by memory ID, never a bare session.

Workflow

  1. Search with memory_smart_search, the user's text as query, targetLayer: "memory", limit: 20, and the requested project/agent scope. These are selected relevance matches, not an exhaustive inventory.
  2. Show what matched: memory ids, titles, and scope. Redact secret values. Ask for explicit confirmation. Do not proceed on silence or a vague "sure, whatever".
  3. On confirmation, call memory_governance_delete with memoryIds as a comma-separated string and optional reason (default plugin skill request).
  4. Observation or whole-session erasure is not supported by this operation. Explain that limit before proceeding; never label selected memory deletion as a complete session wipe. Do not pass observation IDs or a sessionId.
  5. Lessons are separate: delete one with memory_lesson_delete and its lessonId; memory_governance_delete does not touch lessons.
  6. Check deleted, notFound, and failed in the response. Report actual deletions and unresolved IDs separately. Recheck the selected IDs before retrying a failed request; an interrupted response may hide a completed write.

Anti-patterns

WRONG: search returns matches, you immediately call memory_governance_delete without showing them or waiting for a yes.

RIGHT: list the matches, ask "Delete these 2? (yes/no)", and only delete after an explicit yes.

Checklist

  • Matches were shown to the user before any delete.
  • An explicit yes was received, not assumed.
  • memoryIds holds real ids from the search, never a bare sessionId.
  • Final message states the actual count deleted.

See also

  • remember: the write side; forget is its undo.
  • recall: find the exact memory id before deleting.

Troubleshooting

See TROUBLESHOOTING.md if memory_smart_search or memory_governance_delete is not available.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert25d4 checks · Risk HIGH
  • Gen Agent Trust Hub25d

    The skill facilitates the deletion of stored agent memories with safety features like secret redaction and mandatory user confirmation. However, the troubleshooting documentation instructs the agent to access sensitive local credential files (~/.agentmemory/.env and ~/.agentmemory/secret) to authenticate REST calls, which is a high-risk credential access pattern. The skill also processes untrusted user input for searches, creating a potential indirect prompt injection surface.

  • Socket26d

    No alerts

  • Snyk26d

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 5c9e2e6. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated last month
argument-hint
[what to forget - session ID, file path, or search term]
user-invocable
true

README badge

README badge for rohitg00/agentmemory/forget