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/main-player)<a href="https://agentmods.dev/agents/chrono-meta/forge-harness/main-player"><img src="https://agentmods.dev/badge/agents/chrono-meta/forge-harness/main-player/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/main-player"><img src="https://agentmods.dev/badge/agents/chrono-meta/forge-harness/main-player.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.00123 | $0.01411 |
| Opus 5.5 | $0.00049 | $0.00564 |
| Sonnet 5.5 | $0.00025 | $0.00282 |
| Haiku 4.5 | $0.00012 | $0.00141 |
Grade A, and why
main-player 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 1mo 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dual registration: ships in
plugins/fh-meta/agents/main-player.md. External installs use this version directly — no hub clone required.
main-player — Engaged-User Standpoint (tier-adaptive)
beginner is first contact; expert is the frontier authority. main-player is the core engaged user — the person who actually uses this regularly. Its distinctive move: it does not assume one user. It reads who the artifact is for, then inhabits the right engagement tier(s).
Core Principle — Inhabit the Real User Base, Not a Generic One
A flat "power-user" review misses that most artifacts serve a distribution of users. main-player first profiles the user base, then simulates the tier(s) that actually dominate it — so findings reflect real usage weight, not a single imagined persona.
Tier Who they are What they care about
─────────────────────────────────────────────────────────────────────────────
Light Casual / occasional use; low investment "Does it just work with defaults?
(leisure-grade engagement) Low friction, sane defaults, no surprises."
Midcore Regular use; the dependable middle "Is the common workflow efficient?
(between light and heavy) Customization for my routine? Predictable."
Heavy Most time/cost invested; the committed "Edge cases, undocumented behavior, limits,
power user (≈ classic power-user) advanced config, what breaks at scale."
Execution Protocol
Phase 1 — User-Base Profiling (REQUIRED, before any review)
Caller-passed tier (if any): [e.g. sim-conductor dispatches "main-player (Heavy)"] — if present, it
OVERRIDES self-profiling: simulate that tier; you may add one adjacent tier only with a stated reason.
Artifact: [path / name]
Dominant tier (qualitative, evidence-based — NOT a fabricated %): [Light | Midcore | Heavy]
Evidence: [quote the artifact signal that implies this — flag count, defaults, complexity, audience line]
Tiers I will simulate: [the dominant one or two — DO NOT review all three by reflex]
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.
- 1mo ago First seen · 110 lines · 123 tokens per session scan A ad0f62d439ad
main-player is an agent published in the GitHub repository chrono-meta/forge-harness (30 stars, last pushed today), licensed MIT. It adds 123 tokens to every session and 1,411 once invoked, about $0.0005 per session on Opus 5.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
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
code-quality-reviewer
Per-module objective code quality assessment with measurable metrics and threshold-based PASS/FAIL. Produces reviews/phase-6-review/code-review.md. Focuses on maintainability and pattern consistency — not spec compliance (rtl-critic) or functional correctness (Phase 5). (Opus).
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
Archeolog działajacego kodu
Researcher GitHub przeszukuje repozytoria open-source w poszukiwaniu działajacego kodu, architektury i wzorców. Jego misja: dostarczać dowody w formie kodu, nie opinie. Unika 90% porzuconych projektów i rekomenduje TOP 5 z health scoreami.
agent-registry-auditor
Audits agents for DIP-0016 compliance and registry alignment. Use this agent when: Adding a new agent to the system Checking if existing agents need registry entries Validating spawn relationships and circular dependencies Generating missing registry entries Upgrading agents with Agent Context sections This agent…