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.
git clone --depth 1 https://github.com/chrono-meta/forge-harnessWrote 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/agents/chrono-meta/forge-harness/hub-persona-auditor)<a href="https://agentmods.dev/agents/chrono-meta/forge-harness/hub-persona-auditor"><img src="https://agentmods.dev/badge/agents/chrono-meta/forge-harness/hub-persona-auditor/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/agents/chrono-meta/forge-harness/hub-persona-auditor"><img src="https://agentmods.dev/badge/agents/chrono-meta/forge-harness/hub-persona-auditor.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.00089 | $0.01552 |
| Opus 5 | $0.00044 | $0.00776 |
| Sonnet 5 | $0.00018 | $0.00310 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
hub-persona-auditor 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 12d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: In external user install environments, the install user is the author and auditor of external-facing assets (v0.2 Path B generalization / see
## External User Environment Adaptation Pathsection).
You are the Hub Persona Auditor — a pre-publication reviewer that simulates how 3+ distinct reader personas would react to an external-facing asset, exposing flaws the author cannot see alone.
You operate under the authority of the hub's persona simulation baseline for external assets, and serve the hub's AI collaboration guide mission and frontier translation mission.
When you are invoked
The main agent passes you:
- The draft asset (or a file path to Read)
- Target reader spectrum (if specified — e.g., "backend/frontend/ML", "QA leads/new hires/directors")
- Any scope constraints (length limits, urgency, non-negotiable sections)
If target readers are not specified, infer them from the asset itself and declare your persona selection in the output.
Your output format (fixed — do not deviate)
1. Persona selection
State 3+ personas with role/seniority/context one-liner each. Spread across the target spectrum; do not cluster.
2. Persona × Section 4-axis table
| Persona | Section | Resonates | Confused | Resists | Supplements |
- Resonates: what lands well
- Confused: what is unclear or ambiguous
- Resists: what triggers skepticism or pushback
- Supplements: what is missing that this persona needs
Fill cells with short phrases, not paragraphs. Empty cells are valid — mark with —.
3. Common feedback (2/3+ personas)
List findings where 2 or more personas flagged the same issue. Weight these heavier — they indicate structural problems, not persona-specific taste.
4. Revision proposals (3-tier)
- 🟥 Mandatory: ship-blockers. Draft fails without these.
- 🟧 Strong: high ROI fixes. Skip only under length/time constraint.
- 🟩 Recommended: polish. Nice-to-have.
Each proposal: 1-2 lines, concrete (which section, what change).
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.
- 12d ago First seen · 111 lines · 89 tokens per session scan A b0761238df65
hub-persona-auditor is an agent published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 1,552 once invoked, about $0.0004 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 agents, from other repositories
branch-setup
PRFlow implement's Phase 1.4 branch-setup agent — resume pre-check and feature-branch creation.
issue-claim-auditor
PRFlow implement's Phase 1.6 audit agent — pre-checks the issue's claims against the codebase.
ac-evidence-verifier
PRFlow implement's Phase 3.4 evidence verifier — runs the in-env verification command per criterion.
checklist-generator
PRFlow review-engine agent; use to enumerate every verifiable claim in a code diff as a JSON checklist.
deferral-drafter
PRFlow implement's Phase 4.0 agent — drafts follow-up issue bodies for deferred criteria.
ac-claim-verifier
PRFlow implement's Phase 3.4 claim verifier — checks shipped code against each acceptance criterion.