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/pilotspace/add/persona-authornpx skills add pilotspace/ADD --skill persona-authorgit clone --depth 1 https://github.com/pilotspace/ADDWrote 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/pilotspace/add/persona-author)<a href="https://agentmods.dev/skills/pilotspace/add/persona-author"><img src="https://agentmods.dev/badge/skills/pilotspace/add/persona-author.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.00185 | $0.02138 |
| Opus 5 | $0.00093 | $0.01069 |
| Sonnet 5 | $0.00037 | $0.00428 |
| Haiku 4.5 | $0.00018 | $0.00214 |
Grade A, and why
persona-author 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring an ADD persona
A persona is a lens, not a voice — a distilled slice of domain expertise the ADD engine loads onto a beat so a generic agent becomes the specialist. Author for that seam and nothing else: tone belongs to the agent's own voice, the six-dimension self-score lives in the agent (add-worker), and the deliverable's shape lives in the agent's Return contract. A persona that duplicates any of those is dead weight. What a persona owns is judgment: the rules it refuses to wave through, the smells it suspects, the done-bar it measures against.
Two references and one worked example back this workflow — read them as you go:
references/contract.md— the exact engine contract (required/recommended/optional sections, frontmatter field semantics, the flow values and task-kinds taxonomy, the quality WARNs). Read this FIRST; a persona that misses the contract is loaded by no surface.references/patterns.md— the judgment layer distilled from a deep read of strong subagent files plus a diagnosis of the vendored teacher corpus, each pattern with a before/after. This is what separates an expert lens from a keyword list.references/seeding.md— how to SEED a first draft from an existing source (the teacher library at.add/personas-teacher/, or a~/.claude/agents/*.mdsubagent) instead of a blank page: the two source→schema mappings, and the columns a source never supplies (failure-aware Success Metrics,not-when, read-before-you-assert) that you must add yourself.assets/example-persona.md(an I/O lens),assets/example-design-persona.md(a design lens), andassets/example-architect-persona.md(a direction lens) — three fully-worked personas to imitate, not copy. Compare them: the I/O lens carries a design-for-failure ability AND Critical Rule; the design lens omits both (it touches no I/O) and leads with accessibility instead. Proof the patterns are conditional — matched to the surface. The architect lens is the only one of the three with an## Escalationsection: a lens that owns the direction beat has stop-conditions (a frozen contract that would have to move, a reversibility call, an unmeasurable bar) that are distinct from its always-do rules and its guilty-until-proven smells.
What ships with it
6 files 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.
- yesterday Changed c37520550e00
- 6d ago First seen · 123 lines · 185 tokens per session scan A 8ed537e1a525
persona-author is a skill published in the GitHub repository pilotspace/ADD (19 stars, last pushed yesterday), licensed MIT. It adds 185 tokens to every session and 2,138 once invoked, about $0.0009 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 skills, from other repositories
self-review
Self-review a changeset until merge-ready — a fresh-context reviewer checks it as a maintainer would, the author answers every finding, and a compact report for the PR proves the review happened.
refine-ticket
Refine a development ticket — or brainstorm a raw idea — into a validated, self-contained REQUIREMENTS document — the "what", verified against the codebase. Invoke manually only.
review-code-assistant
Assist a human reviewing a pull request or branch locally — diff a source branch against its target (auto-detected or from a PR link) and return concise, human-voice review comments with file and line locations. Read-only, never posts.
review-ticket
Triage a ticket or ticket set before work starts — compare it against the codebase and save a review covering verdict, feature walkthrough, and only the high-cost questions worth raising.
create-implementation-plan
Turn a refined requirements document into a structured implementation PLAN.md a fresh session can execute. Planning only — decides the "how", not the "what". Invoke manually only.
fetch-ticket
Fetch one or more tickets/issues from their tracker (Azure DevOps, Jira, GitHub, …) and save each as a self-contained markdown ticket file. Fetch only — no analysis or planning.