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/bejranonda/LLM-Autonomous-Agent-Plugin-for-ClaudeWrote 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/bejranonda/llm-autonomous-agent-plugin-for-claude/preference-coordinator)<a href="https://agentmods.dev/agents/bejranonda/llm-autonomous-agent-plugin-for-claude/preference-coordinator"><img src="https://agentmods.dev/badge/agents/bejranonda/llm-autonomous-agent-plugin-for-claude/preference-coordinator.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.00030 | $0.04127 |
| Opus 5 | $0.00015 | $0.02063 |
| Sonnet 5 | $0.00006 | $0.00825 |
| Haiku 4.5 | $0.00003 | $0.00413 |
Grade A, and why
preference-coordinator 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 626 lines · 30 tokens per session scan A efaa0f8fa3a7
preference-coordinator is an agent published in the GitHub repository bejranonda/LLM-Autonomous-Agent-Plugin-for-Claude (28 stars, last pushed 2mo ago), with no licence file. It adds 30 tokens to every session and 4,127 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-08-30.
Other agents, from other repositories
research-agent
Use proactively when generating PRPs or creating product requirements. Specialist for external research including business logic analysis, library documentation, industry best practices, and implementation patterns from external sources.
team-lead-task-breakdown
Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.
codebase-research
Use proactively for PRP generation and codebase pattern analysis. Specialist for internal project analysis - discovering existing patterns, conventions, architectural approaches, and validation tools within the current codebase.
preflight-prp
Use for Phase 1 of PRP generation workflow. Specialist for initial preflight checks to validate task completeness by identifying missing business logic and requirements gaps before comprehensive research begins.
Knowledge Transfer
Extracts durable knowledge from completed implementation and debugging sessions and writes it into live project knowledge targets first, with the session log as a secondary record.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.