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/profilesnpx skills add alaarab/phren --skill profilesgit clone --depth 1 https://github.com/alaarab/phrenWhat 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.00015 | $0.00825 |
| Opus 5 | $0.00008 | $0.00413 |
| Sonnet 5 | $0.00003 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
profiles 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 2d 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.
This is a copy
95% identical to phren-profiles — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
phren-profiles - Manage your profiles
Multi-machine only. This skill is for users who sync phren across multiple machines and need to control which projects appear where. If you only use one machine, you can skip this --
phren-synchandles everything you need.
Add projects to profiles, move projects between profiles, create new profiles, and check what's in each one.
Manage which projects appear on which machines by editing your profile definitions. Each machine maps to one profile, and each profile is a list of projects.
Prerequisites
You need a phren repo. The profiles live in ~/.phren/profiles/ and machine mappings live in ~/.phren/machines.yaml.
~/.phren/
profiles/
work.yaml
personal.yaml
machines.yaml
If you don't have a phren repo yet, start with phren-init.
What's a profile?
A profile is a YAML file listing projects for a machine role. Example:
name: work
description: Work laptop with company projects
projects:
- global
- my-api
- frontend
When you sync on a machine mapped to this profile, only those projects appear. Personal projects stay off work machines.
How to use it
"Add a project to a profile"
User says: "add my-project to my work profile"
- Find the profile file:
~/.phren/profiles/work.yaml - Read it and find the
projects:list - Add the project name if it's not already there
- Commit the change
"Create a new profile"
User says: "create a new profile called staging"
- Create a new file:
~/.phren/profiles/staging.yaml - Fill it with the required structure:
name: staging
description: Staging servers and experiments
projects:
- global
- Ask which projects should be in this new profile (can add more later)
- Commit the file
"Show me what's in a profile"
User says: "what's in my personal profile?"
- Find
~/.phren/profiles/personal.yaml - Read it and display the projects list
"Move a project between profiles"
User says: "move my-project from personal to work"
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.
- 2d ago First seen · 122 lines · 15 tokens per session scan A a3eca61b6808
profiles is a skill published in the GitHub repository alaarab/phren (4 stars, last pushed 8d ago), licensed MIT. It adds 15 tokens to every session and 825 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to phren-profiles, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
lark-im
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
organize-threads
猫猫辅助整理未分类 thread，分析标题和元数据，建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.