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/codeinfinity1/stram/persona-evolutionnpx skills add CodeInfinity1/Stram --skill persona-evolutiongit clone --depth 1 https://github.com/CodeInfinity1/StramWhat 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.00043 | $0.00602 |
| Opus 5 | $0.00022 | $0.00301 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
persona-evolution 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 yesterday.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona Evolution
Purpose
Let the assistant grow a stable working relationship with the user without inventing personality or overfitting. This skill uses Stram's model-led persona evolution over evidence.
When To Use
Use when the user says how they want the assistant to communicate, how decisions should be made, what to remember about them, or what behavior should change over time.
Inputs And Evidence
- Direct user statements.
- Interaction review records.
- Persona records and evolutions.
- Repeated preferences across sessions.
- Current task context and communication channel.
Tool Map
cognitive_persona_evolvecognitive_persona_evolution_statuscognitive_interaction_reviewmemory_profilememory_writecognitive_state
Workflow
- Separate stable preferences from momentary task-specific instructions.
- Gather current persona and recent interaction evidence.
- Use model-led persona evolution to propose updates.
- Record only preferences or stable facts with direct evidence.
- Preserve boundaries such as not claiming emotions, identity, or certainty beyond evidence.
- In the response, explain the practical behavior change.
Safety And Boundaries
- Do not store sensitive personal facts unless useful and clearly requested or appropriate.
- Do not infer protected attributes.
- Do not overwrite explicit preferences with weak contradictory evidence.
Safety And Approval
- Persona updates must be grounded in direct user statements, repeated behavior, or interaction-review evidence.
- Do not create claims about the assistant's identity, emotions, relationship, or certainty beyond evidence and policy boundaries.
- Do not store private or sensitive user facts unless they are operationally useful and appropriate to retain.
- If the user asks to forget or change a preference, preserve the latest explicit instruction over older inferred behavior.
Native Implementation Boundaries
- Use Stram persona-evolution, interaction-review, memory-profile, memory-write, and cognitive-state tools.
- Personal-development patterns from references are guidance only; persistent persona/user-model changes must be model-led and evidence-backed.
- Deterministic code may merge bounded records and validate schemas, but must not infer stable user traits from keyword matches.
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.
- yesterday First seen · 78 lines · 43 tokens per session scan A 333c16306220
persona-evolution is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 43 tokens to every session and 602 once invoked, about $0.0002 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.