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 skills add event4u-app/agent-config --skill persona-improvementgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/persona-improvement)<a href="https://agentmods.dev/skills/event4u-app/agent-config/persona-improvement"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/persona-improvement/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/event4u-app/agent-config/persona-improvement"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/persona-improvement.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00953 |
| Opus 5 | $0.00017 | $0.00477 |
| Sonnet 5 | $0.00007 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
persona-improvement 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
persona-improvement
The persona analog of skill-improvement-pipeline:
feed a persona a sample of recent corrections/failures where its review lens
should have caught something and didn't, and tighten its Unique Questions
so the lens fires next time. Access ergonomics, not new capability — it only
sharpens an existing persona, never creates one.
When to use
- The user explicitly says "improve / refine this persona" or "the lens keeps missing X".
- A correction sample exists (review misses, repeated feedback) that a persona's questions should have surfaced.
Do NOT use for:
- Creating a new persona (that is
persona-governance+ the authoring flow). - Editing a persona's identity/scope (a breaking change → new id per
persona-governance). - A one-off miss with no pattern — one anecdote is not a refinement signal.
Procedure
- Gather the correction sample. Collect the recent misses/corrections tied to this persona's domain (from the conversation, feedback notes, or a review log). If fewer than ~3 distinct misses, STOP — no pattern yet; say so.
- Locate the gap. For each miss, name the question the persona should have asked that would have surfaced it. Cluster the misses into ≤ 2 recurring gaps.
- Propose tightened
Unique Questions. Rewrite or add questions that close the gaps — concrete and answerable-from-the-diff, not vague ("does this add a second branch on the same enum?" beats "is the design good?"). Keep the section ≥ 3 questions (persona-governanceschema floor). - Governance gate (mandatory). Before writing, confirm with
persona-governance: the edit is a same-id refinement (not a scope/identity change — those need a new id); the persona keeps ≥ 1 skill citation; the file still passes the skill linter (tier/wing/section/line budget). A scope change is out of scope for this loop. - Apply + verify. Edit only the
Unique Questionssection; run./scripts-run src/scripts/skill_linteron the persona file and confirm 0 errors; show the before/after questions.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 83 lines · 35 tokens per session scan A a18740dcbf07
persona-improvement is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 953 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-09-04.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.