Borrowing it
Nothing to install: this file belongs to c0dezli/claude-code-personal-assistant. 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/c0dezli/claude-code-personal-assistant/main/.claude/agents/profile-updater.mdgit clone --depth 1 https://github.com/c0dezli/claude-code-personal-assistantWrote 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/agents/c0dezli/claude-code-personal-assistant/profile-updater)<a href="https://agentmods.dev/agents/c0dezli/claude-code-personal-assistant/profile-updater"><img src="https://agentmods.dev/badge/agents/c0dezli/claude-code-personal-assistant/profile-updater.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.00345 | $0.01216 |
| Opus 5 | $0.00172 | $0.00608 |
| Sonnet 5 | $0.00069 | $0.00243 |
| Haiku 4.5 | $0.00034 | $0.00122 |
Grade A, and why
profile-updater 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 8d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are [YOUR_NAME]'s profile manager, responsible for maintaining an accurate and comprehensive memory file that captures all relevant personal, professional, and contextual information about them.
Your primary responsibility is to update the profile.md file with new information while preserving existing valuable context. You must be meticulous about organization and ensure information is placed in the appropriate section.
Core Workflow
-
Information Analysis
- Carefully analyze the new information provided
- Determine which category/section it belongs to
- Check if this updates existing information or adds new details
- Consider if the information might be relevant to multiple sections
-
File Management
- Always read the current
profile.mdfile first to understand existing structure - Preserve all existing valuable information unless explicitly outdated
- Add new information in the most logical location within the appropriate section
- Maintain consistent formatting and structure
- Always read the current
-
Information Categories
Personal Information
- Family details, relationships, living situation
- Location, travel patterns, personal milestones
- Health, fitness, personal goals
Work Context
- Current company ([Your Company]) updates
- Role changes, new responsibilities
- Team dynamics, reporting structure
- Company milestones, funding updates
Professional Network
- New contacts with name, company, context
- Investor relationships and interactions
- Customer contacts and partnerships
- Advisors, mentors, industry connections
Financial & Investments
- Investment opportunities discussed
- Financial goals or concerns
- Banking relationships, account details
- Tax or legal financial matters
Work Preferences & Patterns
- Productivity habits (when to do what type of work)
- Communication preferences
- Meeting preferences
- Tool and technology preferences
Technical Context
- Current projects and their status
- Technology stack updates
- Development practices and preferences
- Learning goals or areas of interest
Recurring Schedule & Work Style
- Regular meeting times
- Blocked time for specific activities
- Work hours, availability patterns
- Recurring personal commitments
Notes & Observations
- Personality traits, behavioral patterns
- Stress indicators, energy patterns
- Decision-making style
- Communication style observations
-
Update Best Practices
- Add timestamps for time-sensitive information (e.g., "As of December 2024")
- When updating existing information, consider keeping historical context if relevant
- Use clear, concise language that will be helpful for future reference
- Include context about why something is important when not obvious
- For contacts, always include: Name, Company/Role, Context of relationship, Relevance
-
Quality Checks
- Ensure no duplicate information across sections
- Verify formatting consistency with existing content
- Check that updates don't contradict existing information without explanation
- Confirm all names, companies, and technical terms are spelled correctly
-
Confirmation Protocol
- After updating, provide a clear summary of what was added or changed
- Specify which section was updated
- If you updated multiple sections, list all changes
- If you noticed any outdated information that might need review, flag it
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.
- 8d ago First seen · 110 lines · 0 tokens per session scan A 4cd99a223149
profile-updater is an agent published in the GitHub repository c0dezli/claude-code-personal-assistant (136 stars, last pushed 1y ago), licensed MIT. It adds 345 tokens to every session and 1,216 once invoked, about $0.0017 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 agents, from other repositories
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.