Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/alaarab/phren/phren-initnpx skills add alaarab/phren --skill phren-initgit clone --depth 1 https://github.com/alaarab/phrenWrote 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/alaarab/phren/phren-init)<a href="https://agentmods.dev/skills/alaarab/phren/phren-init"><img src="https://agentmods.dev/badge/skills/alaarab/phren/phren-init.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 | $0.00026 | $0.01381 |
| Opus 5 | $0.00013 | $0.00691 |
| Sonnet 5 | $0.00005 | $0.00276 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
phren-init 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- init — 92% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
phren-init - Scaffold a new project
Set up a new project in phren with summary, CLAUDE.md, task, and skill templates.
Add a new project to your phren instance, or bootstrap phren itself if you're starting fresh.
Usage
phren-init my-new-project # scaffold a specific project
phren-init # list existing projects, suggest unconfigured ones
First: find or create the phren directory
PHREN_DIR="${PHREN_DIR:-$HOME/.phren}"
ls "$PHREN_DIR" 2>/dev/null
If the phren directory doesn't exist, offer to create it:
"No phren repo found. Want me to create one at ~/.phren? This will set up the base directory structure (global/, profiles/, machines.yaml)."
If the user says yes, create the base structure:
mkdir -p "$PHREN_DIR"/{global/skills,profiles}
# Create a starter machines.yaml
# Create a starter profile
Then continue with the project scaffolding below.
With a project name
1. Check it doesn't already exist
ls "$PHREN_DIR/<project-name>/" 2>/dev/null
If it exists, tell the user and ask if they want to reset it or just update specific files.
2. Create the project directory
mkdir -p "$PHREN_DIR/<project-name>/skills"
3. Create summary.md
This is the project's identity card. Five lines, no more.
# <project-name>
What: <one sentence about what this project does>
Stack: <languages, frameworks, key deps>
Status: <active / maintenance / new / archived>
Run: <the main command to start it, e.g. "npm run dev">
Watch out: <the one thing that trips people up>
Ask the user for these if you can't figure them out from the project directory. If the project directory exists on disk (e.g. ~/<project-name>/), read its package.json, pyproject.toml, README, or similar to pre-fill.
4. Create CLAUDE.md
# <project-name>
<One paragraph: what this project is and what it does.>
## Commands
Architecture
Conventions
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.
- 3d ago First seen · 217 lines · 26 tokens per session scan A d67893b4e87d
phren-init is a skill published in the GitHub repository alaarab/phren (4 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 1,381 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…