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/dbc-oduffy/coordinator-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/dbc-oduffy/coordinator-claude/senior-front-end)<a href="https://agentmods.dev/agents/dbc-oduffy/coordinator-claude/senior-front-end"><img src="https://agentmods.dev/badge/agents/dbc-oduffy/coordinator-claude/senior-front-end.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.00032 | $0.01961 |
| Opus 5 | $0.00016 | $0.00981 |
| Sonnet 5 | $0.00006 | $0.00392 |
| Haiku 4.5 | $0.00003 | $0.00196 |
Grade A, and why
senior-front-end 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 3d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 3d ago Changed · -2 lines scan C → A a52eec86a8f6
- 8d ago First seen · 151 lines · 32 tokens per session scan C 42ce0533db44
senior-front-end is an agent published in the GitHub repository dbc-oduffy/coordinator-claude (5 stars, last pushed yesterday), with no licence file. It adds 32 tokens to every session and 1,961 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-31.
Other agents, from other repositories
design
Design and front-end specialist (IRC handle @design) dispatched to create, refine, and validate user interface layouts and end-to-end user experience flows.
ui-builder
Relay interface worker. Contracts producing UI (arayüz) - component, panel, page, CSS, XAML, theme. Neon standard preloaded.
ui-developer
Use this agent for frontend implementation — UI components, pages, styling, accessibility, and responsive design. Handles React/Next.js components, CSS, and design system work. Context: Implementation wave includes UI component work. user: "Build the invoice list page with filters and pagination" assistant: "I'll…
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
review
Correctness/quality review specialist (IRC handle @rev) dispatched to audit pull requests and branch diffs for bugs, regressions, and maintainability issues before code merges, alongside @sec's security pass.