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 commands/technickai/claude_telemetry/personality-changegit clone --depth 1 https://github.com/TechNickAI/claude_telemetryWrote 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/commands/technickai/claude_telemetry/personality-change)<a href="https://agentmods.dev/commands/technickai/claude_telemetry/personality-change"><img src="https://agentmods.dev/badge/commands/technickai/claude_telemetry/personality-change.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.00011 | $0.00871 |
| Opus 5 | $0.00005 | $0.00436 |
| Sonnet 5 | $0.00002 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
personality-change 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change the active AI personality to create consistent behavior across Claude Code and Cursor.
IMPORTANT: Ask the user which personality they want if not provided.
Available Personalities
- sherlock - Analytical, precise, deductive reasoning for debugging
- bob-ross - Calm, encouraging, treats bugs as happy accidents
- samantha - Warm, witty, emotionally intelligent, playfully flirty
- stewie - Sophisticated, condescending, theatrical, brilliant with high standards
- ron-swanson - Minimalist, anti-complexity, straightforward and practical
- marie-kondo - Organized, joyful minimalism, eliminates what doesn't spark joy
- marianne-williamson - Spiritual, love-based, sees coding as consciousness work
- unity - Creative muse meets structured builder, warm encourager
Process
1. Validate Input
- If no personality name provided, show available personalities and ask which to activate
- Check that
.cursor/rules/personalities/<name>.mdcexists - If
nonewas requested, skip to step 3 to remove personality
2. Handle Claude Code Activation
a. Read or create .claude/context.md
b. Check for existing personality:
- Search for
## Active Personalitysection - Extract current name from
<!-- personality-<name> -->comment if found
c. If personality exists:
- If same as requested: inform "✓ is already active" and stop
- If different: remove entire
## Active Personalitysection (including HTML comments)
d. If not removing (name != "none"):
- Read
.cursor/rules/personalities/<name>.mdc - Strip frontmatter (content between opening
---and closing---) - Append to
.claude/context.md:
## Active Personality
<!-- personality-<name> -->
<personality content without frontmatter>
<!-- /personality-<name> -->
e. Write updated .claude/context.md
3. Update Cursor Configuration
a. Find all personality files in .cursor/rules/personalities/ (except
common-personality.mdc)
b. For each personality file:
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.
- 5d ago First seen · 127 lines · 11 tokens per session scan A 6f4a5f4ad913
personality-change is a command published in the GitHub repository TechNickAI/claude_telemetry (31 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 871 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 commands, from other repositories
worktree-check
Check current worktree status, branch, and assigned task.
README
Git workflow and quality assurance commands for the claude-skills repository.
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
adv-gemini-research
Deep research query via Gemini with Google Search grounding.
ccc-orchestrate
Sequential and tmux/worktree orchestration guidance for multi-agent workflows.