Agent MemoryBLOCK
📦 Repomix is a powerful tool that packs your entire repository into a single, AI-friendly file. Perfect for when you need to feed your codebase to Large Language Models (LLMs) or other AI tools like Claude, ChatGPT, DeepSeek, Perplexity, Gemini, Gemma, Llama, Grok, and more.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Special thanks to:
Warp, built for coding with multiple AI agents
Available for MacOS, Linux, & Windows
CodeRabbit | AI Code Reviews
Cut code review time & bugs in half, instantly.
Pack your codebase into AI-friendly formats
Use Repomix online! 👉 repomix.com
Need discussion? Join us on Discord! Share your experience and tips Stay updated on new features Get help with configuration and usage
[](https://www.npmjs.com/package/repomix) [](https://www.npmjs.com/package/repomix) [](https://github.com/yamadashy/repomix/actions?query=workflow%3A"ci") ["
---
# Repomix — Codebase Packer & Analyzer
Pack entire codebases into a single, AI-friendly file for analysis. Repomix intelligently collects repository files, respects `.gitignore`, runs security checks, and generates structured output optimized for LLM consumption.
## When to Use
- "Analyze this repo" / "Explore this codebase"
- "What's the structure of facebook/react?"
- "Find all authentication-related code"
- "How many tokens is this project?"
- "Pack this repo for AI analysis"
- "Show me the main components of vercel/next.js"
## Quick Reference
### Pack a Remote Repository
```bash
npx repomix@latest --remote <owner/repo> --output /tmp/<repo-name>-analysis.xml
```
Always output to a temporary directory (`/tmp` on Unix, `%TEMP%` on Windows) for remote repositories to avoid polluting the user's working directory.
### Pack a Local Directory
```bash
npx repomix@latest [directory] --output /tmp/<name>-analysis.xml
```
### Key Options
| Option | Description |
|--------|-------------|
| `--style <format>` | Output format: `xml` (default, recommended), `markdown`, `plain`, `json` |
| `--compress` | Tree-sitter compression (~70% token reduction) — use for large repos |
| `--include <patterns>` | Include only matching patterns (e.g., `"src/**/*.ts,**/*.md"`) |
| `--ignore <patterns>` | Additional ignore patterns |
| `--output <path>` | Custom output path (default: `repomix-output.xml`) |
| `--remote-branch <name>` | Specific branch, tag, or commit (for remote repos) |
## Workflow
### Step 1: Pack the Repository
Choose the appropriate command based on the target:
```bash
# Remote repository (always output to /tmp)
npx repomix@latest --remote yamadashy/repomix --output /tmp/repomix-analysis.xml
# Large remote repo with compression
npx repomix@latest --remote facebook/react --compress --output /tmp/react-analysis.xml
# Local directory
npx repomix@latest ./src --output /tmp/src-analysis.xml
# Specific file types only
npx repomix@latest --include "**/*.{ts,tsx,js,jsx}" --output /tmp/filtered-analysis.xml
```
### Step 2: Check Command Output
The command displays:
- **Files processed**: Number of files included
- **Total characters**: Size of content
- **Total tokens**: Estimated AI tokens
- **Output file location**: Where the file was saved
Note the output file location for subsequent analysis.
### Step 3: Analyze the Output
**Structure overview:**
1. Search for the file tree section (near the beginning of the output)
2. Check the metrics summary for overall statistics
**Search for patterns** (use the output file path from Step 2):
```bash
# Find exports and main entry points
grep -iE "export.*function|export.*class" <output-file>
# Search with context
grep -iE -A 5 -B 5 "authentication|auth" <output-file>
# Find API endpoints
grep -iE "router|route|endpoint|api" <output-file>
# Find database models
grep -iE "model|schema|database|query" <output-file>
```
**Read specific sections** using offset/limit for large outputs.
### Step 4: Report Findings
- **Metrics**: Files, tokens, size from command output
- **Structure**: Directory layout from file tree analysis
- **Key findings**: Based on pattern search results
- **Next steps**: Suggestions for deeper exploration
## Best Practices
1. **Use `--compress` for large repos** (>100k lines) to reduce token usage by ~70%
2. **Use pattern search first** before reading entire output files
3. **Use a temporary directory for output** (`/tmp` on Unix, `%TEMP%` on Windows) to keep the user's workspace clean
4. **Use `--include` to focus** on specific parts of a codebase
5. **XML is the default and recommended format** — it has clear file boundaries for structured analysis
## Output Formats
| Format | Best For |
|--------|----------|
| XML (default) | Structured analysis, clear file boundaries |
| Markdown | Human-readable documentation |
| Plain | Simple grep-friendly output |
| JSON | Programmatic/machine analysis |
## Error Handling
- **Command fails**: Check error message, verify repository URL/path, check permissions
- **Output too large**: Use `--compress`, narrow scope with `--include`
- **Network issues** (remote): Verify connection, suggest local clone as alternative
- **Pattern not found**: Try alternative patterns, check file tree to verify files exist
## Security
Repomix automatically excludes potentially sensitive files (API keys, credentials, `.env` files) through built-in security checks. Trust its security defaults unless the user explicitly requests otherwise.Trust audit
BLOCKgrade F · trust 44/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (10 observation(s))
- Network
- declared (6 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (25)
'metadata.google.internal', // GCP metadata, by name
.claude/agents
.claude/commands
.claude/skills/agent-carnet
.claude/skills/contextual-commit
.claude/skills/repomix-explorer
const apiKey = "sk_live_1234567890abcdef";
GitHub Token: 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
-----BEGIN RSA PRIVATE KEY-----
xoxa-23984754863-2348975623103
xoxb-23984754863-2348975623103
const apiKey = "sk_live_1234567890abcdef";
API_KEY=sk_live_1234567890abcdef
.codecov.yml
.coderabbit.yaml
.oxlintrc.json
.pinact.yaml
.repomixignore
return createHash('md5').update(joined).digest('hex');const digest = createHash('md5').update(content).digest('hex').slice(0, 16);'~/.ssh/id_rsa',
import { loadFileConfig, mergeConfigs } from '../../config/configLoad.js';} from '../../config/configSchema.js';
import { logFileProcessorStatus } from '../../core/file/fileProcessorRun.js';import { readFilePathsFromStdin } from '../../core/file/fileStdin.js';Gates applied: no_behavioural_pass.
2ab8ea23f898full audit observations/trust-audit/skill/yamadashy__agent-memory.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-22 | 2ab8ea23f898 | BLOCK | F | 44 | first audit |
Questions
What does the agent-memory — yamadashy/repomix skill do?
📦 Repomix is a powerful tool that packs your entire repository into a single, AI-friendly file. Perfect for when you need to feed your codebase to Large Language Models (LLMs) or other AI tools like Claude, ChatGPT, DeepSeek, Perplexity, Gemini, Gemma, Llama, Grok, and more.
Is agent-memory — yamadashy/repomix safe to install?
No — not without reading the findings first. The audit graded it F (44/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on.
What can agent-memory — yamadashy/repomix access on my machine?
The audit observed that it reaches the network and reads or writes files. Each of those is consistent with what it says it does. Secrets in the source: found — see the findings.
Which assistants does agent-memory — yamadashy/repomix work with?
Its documentation mentions claude-code, claude-desktop, codex, copilot, cursor, gemini-cli and openclaw. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (2ab8ea23f898), read on 2026-10-22. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/yamadashy/agent-memory/)
Not your listing, or something out of date? Claim or update your listing.