AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Auto Memory Tool Permission Fencing

skill-ychampion-cskill-agents-auto-memory-tool-permission-fencing · by ychampion

Gate every tool call in the auto-memory extract agent so only safe read-only actions and targeted writes execute.

No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-ychampion-cskill-agents-auto-memory-tool-permission-fencing

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-ychampion-cskill-agents-auto-memory-tool-permission-fencing)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Auto Memory Tool Permission Fencing? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

SKILL: Auto Memory Tool Permission Fencing

Domain: permissions Trigger: Apply whenever a background auto-memory agent must be limited to safe read-only commands and writes that target the memory directory. Source Pattern: Distilled from reviewed permission, shell-safety, and worktree-management implementations.

Core Method

Route every tool call from the auto-memory agent through one permission adapter. That adapter should allow only safe read operations plus tightly scoped writes into the memory directory, while rejecting all other commands with a consistent denial message. Shell access must be limited to a vetted read-only subset, and file edits must be checked against the memory path boundary before execution. This keeps the background extractor useful without giving it broad workspace or shell power.

Key Rules

  • Give the forked agent one shared permission wrapper so every tool request is validated the same way before execution.
  • Allow REPL only if it is necessary; the inner REPL will re-invoke the same guard so the policy stays intact.
  • On denial, emit a clear message referencing the restricted commands list so the agent knows that only auto-memory-safe tools remain.
  • Reject any Write/Edit outside memory, and treat Allow decisions as explicit acknowledgments that the target path belongs to the auto-memory directory.

Example Application

When spinning up an auto-memory extractor, pass this guard into the agent’s context so the model can safely Read the session transcript and Write the new md files without accidentally invoking git push or editing unrelated workspace files.

Anti-Patterns (What NOT to do)

  • Don’t grant the forked agent unrestricted Bash access; even read-only commands should be explicitly vetted to prevent injection.
  • Don’t assume tool schema validation alone is enough; permission policy still needs to re-check whether the action is safe and properly scoped.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.