Borrowing it
Nothing to install: this file belongs to agent-sh/agentsys. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agent-sh/agentsys/main/.kiro/skills/enhance-claude-memory/SKILL.mdgit clone --depth 1 https://github.com/agent-sh/agentsysWrote 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/agent-sh/agentsys/enhance-claude-memory)<a href="https://agentmods.dev/skills/agent-sh/agentsys/enhance-claude-memory"><img src="https://agentmods.dev/badge/skills/agent-sh/agentsys/enhance-claude-memory.svg" alt="Measured on agentmods" height="20"></a>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.00022 | $0.02551 |
| Opus 5 | $0.00011 | $0.01275 |
| Sonnet 5 | $0.00004 | $0.00510 |
| Haiku 4.5 | $0.00002 | $0.00255 |
Grade A, and why
enhance-claude-memory 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 7d 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 — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
enhance-claude-memory
Analyze project memory files (CLAUDE.md, AGENTS.md) for optimization.
Cross-Tool Detection
Searches for project memory files in order:
- CLAUDE.md (Claude Code)
- AGENTS.md (OpenCode, Codex)
- .github/CLAUDE.md
- .github/AGENTS.md
File Hierarchy (Reference)
CLAUDE.md (Claude Code):
| Location | Scope |
|---|---|
~/.claude/CLAUDE.md |
Global (all projects) |
.claude/CLAUDE.md or ./CLAUDE.md |
Project root |
src/.claude/CLAUDE.md |
Directory-specific |
AGENTS.md (OpenCode, Codex, and other AI tools):
| Location | Scope |
|---|---|
~/.config/opencode/AGENTS.md or ~/.codex/AGENTS.md |
Global (all projects) |
.opencode/AGENTS.md or ./AGENTS.md |
Project root |
src/AGENTS.md |
Directory-specific |
Both files serve the same purpose: project memory for AI assistants. Use CLAUDE.md for Claude Code projects, AGENTS.md for cross-tool compatibility, or both for maximum coverage.
Workflow
- Find - Locate CLAUDE.md or AGENTS.md in project
- Read - Load content and README.md for comparison
- Analyze - Run all pattern checks
- Validate - Check file/command references against filesystem
- Measure - Calculate token metrics and duplication
- Report - Generate structured markdown output
Detection Patterns
1. Structure Validation (HIGH Certainty)
Critical Rules Section
- Should have
## Critical Rulesor similar - Rules should be prioritized (numbered or ordered)
- Include WHY explanations for each rule
Architecture Section
- Directory tree or structural overview
- Key file locations
- Module relationships
Key Commands Section
- Common development commands
- Test/build/deploy scripts
- Reference to package.json scripts
2. Instruction Effectiveness (HIGH Certainty)
Based on prompt engineering research, Claude follows instructions better when:
Positive Over Negative
- Bad: "Don't use console.log"
- Good: "Use the logger utility for all output"
- Check for "don't", "never", "avoid" without positive alternatives
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.
- 7d ago First seen · 388 lines · 22 tokens per session scan A c19248087939
enhance-claude-memory is a skill published in the GitHub repository agent-sh/agentsys (982 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 2,551 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
refactor
Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
tech-debt-audit
Thorough, file-cited technical debt audit across 9 dimensions using AST-grep (tree-sitter), grep, LSP, and language-native tooling. Produces TECHDEBTAUDIT.md with severity, effort estimates, and prioritized fixes. Use when asked for codebase health check, tech debt audit, architecture review, code quality assessment…