Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sabbour/agentweavernpx agentmods add skills/sabbour/agentweaver/persona-briefsWrote 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/sabbour/agentweaver/persona-briefs)<a href="https://agentmods.dev/skills/sabbour/agentweaver/persona-briefs"><img src="https://agentmods.dev/badge/skills/sabbour/agentweaver/persona-briefs/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/sabbour/agentweaver/persona-briefs"><img src="https://agentmods.dev/badge/skills/sabbour/agentweaver/persona-briefs.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.00000 | $0.01292 |
| Opus 5 | $0.00000 | $0.00646 |
| Sonnet 5 | $0.00000 | $0.00258 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
persona-briefs 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 6d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness scenario catalog and generation contract
Use this contract when you need to discover the current built-in scenario/persona catalog for one harness surface, or generate a reviewed new persona core and surface adapter for a new test intent.
Generators in this package are prompt assemblers only. They never call a model, write a persona file, scaffold a harness scenario module, or bypass review.
Before starting, read scripts/harness-shared/learnings.md's scenario-design-note
entries — several existing adapters intentionally stop before full completion (a
review/confirmation gate), which is by design, not a stuck/broken run.
Retrieve existing scenarios
Run these commands from the repository root:
API surface
List the deterministic built-in API scenario modules:
node scripts/api-harness/run-persona.mjs --list
Output: a stable text list of scenario IDs from scripts/api-harness/scenarios/*.mjs.
Use one of those IDs with --scenario <id> when invoking the API harness.
UI surface
List the built-in UI scenario starters:
node scripts/ui-harness/agent-driver-ui/tools.mjs list-scenarios
Output: JSON with surface: "ui", mode: "persona-adapter", and scenarios, the
persona IDs that currently have reviewed UI adapters under
scripts/persona-briefs/surfaces/*.ui.md. Use one of those IDs with
init --persona <id>.
MCP surface
List the built-in MCP scenario starters:
node scripts/mcp-harness/run-persona.mjs --list
Output: JSON with surface: "mcp", mode: "persona-adapter", and scenarios, the
persona IDs that currently have reviewed MCP adapters under
scripts/persona-briefs/surfaces/*.mcp.md. Drive one of them dynamically with
run-persona.mjs (a sub-agent dispatched under scripts/mcp-harness/agent-driver/AGENT.md
discovers the live tool menu and decides each call), or run the fixed
smoke/mcp-cli-smoke.mjs connectivity/capability tripwire; see
scripts/mcp-harness/SKILL.md. The same --list also works from
smoke/mcp-cli-smoke.mjs.
What ships with it
26 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.
- catalog.json 2.8 KB
- find-similar.mjs 3.3 KB runs code
- generate-adapter.mjs 2.2 KB runs code
- generate-core.mjs 2.8 KB runs code
- index.mjs 3.3 KB runs code
- package.json 301 B
- persona-schema.mjs 3.6 KB runs code
- personas/jordan.md 2.2 KB
- personas/maya.md 2.0 KB
- personas/oracle.md 3.0 KB
- personas/priya.md 2.0 KB
- README.md 948 B
- surfaces/jordan.api.md 692 B
- surfaces/jordan.mcp.md 468 B
- surfaces/jordan.ui.md 686 B
- surfaces/maya.api.md 681 B
- surfaces/maya.mcp.md 449 B
- surfaces/maya.ui.md 640 B
- surfaces/oracle.api.md 1.9 KB
- surfaces/priya.api.md 703 B
- surfaces/priya.mcp.md 444 B
- surfaces/priya.ui.md 650 B
- surfaces/README.md 266 B
- test/find-similar.test.mjs 2.6 KB runs code
- test/index.test.mjs 2.7 KB runs code
- test/persona-schema.test.mjs 1.9 KB runs code
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.
- 6d ago First seen · 151 lines · 0 tokens per session scan A a1c83ca458e4
persona-briefs is a skill published in the GitHub repository sabbour/agentweaver (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,292 tokens. 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-03.
Other skills, from other repositories
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
product-test
Use this skill to define the observable behavior that must be true for a story or feature to be considered done. It turns product context into concise, testable Given/When/Then scenarios that engineers and QA can verify without guessing intent.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.