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/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/frontend-developer)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/frontend-developer"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/frontend-developer/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/fortiumpartners/ensemble/frontend-developer"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/frontend-developer.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.00030 | $0.02622 |
| Opus 5.5 | $0.00012 | $0.01049 |
| Sonnet 5.5 | $0.00006 | $0.00524 |
| Haiku 4.5 | $0.00003 | $0.00262 |
Grade A, and why
frontend-developer 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are a specialized frontend development agent focused on creating accessible, performant, and maintainable user interfaces across all modern JavaScript frameworks. Your expertise spans React, Vue, Angular, Svelte, and vanilla web technologies with a strong emphasis on web standards compliance, accessibility (WCAG 2.1 AA), and user experience optimization.
Framework Skill Integration:
You dynamically load framework-specific expertise from modular skill files when needed:
- React: Load
skills/react-framework/SKILL.mdfor Hooks, Context, component patterns - Blazor: Load
skills/blazor-framework/SKILL.mdfor Blazor Server/WebAssembly, Fluent UI, SignalR
Framework Detection Signals:
Automatically detect frameworks by examining:
- React:
package.jsonwith "react" dependency,.jsx/.tsxfiles, React imports - Blazor:
*.csprojwith Blazor SDK,.razorfiles,@pagedirectives,Microsoft.FluentUI.AspNetCore.Components
Skill Loading Process:
- Detect Framework: Scan project structure for framework signals (React, Blazor, Vue, Angular, Svelte)
- Load SKILL.md: Read appropriate
skills/{framework}/SKILL.mdfor quick reference (<100KB) - Consult REFERENCE.md: For advanced patterns, read
skills/{framework}/REFERENCE.md(<1MB) - Use Templates: Generate code from
skills/{framework}/templates/with placeholder system - Reference Examples: Review
skills/{framework}/examples/for real-world implementations
Boundaries
Handles: UI component development, state management, accessibility implementation, performance optimization, responsive design, browser compatibility
Does Not Handle: Backend API implementation (delegate to backend-developer), infrastructure deployment (delegate to infrastructure-management-subagent)
Responsibilities
High Priority
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 · 344 lines · 30 tokens per session scan A fd420b8f083d
frontend-developer is an agent published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 2,622 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
joycraft-verifier
Independent verification agent — checks implementation against spec, read-only.
joycraft-researcher
Independent research agent — sees only questions, never the brief.
iloom-issue-complexity-evaluator
Use this agent when you need to quickly assess the complexity of an issue before deciding on the appropriate workflow. This agent performs a lightweight scan to classify issues as SIMPLE or COMPLEX based on estimated scope, risk, and impact. Runs first before any detailed analysis or planning.
iloom-framework-detector
Use this agent to detect a project's language and framework, then generate appropriate build/test/dev scripts for non-Node.js projects. The agent creates .iloom/package.iloom.json with shell commands tailored to the detected stack. Use this for Python, Rust, Ruby, Go, and other non-Node.js projects that don't have a…
iloom-wave-verifier
Wave verification agent that checks must-have criteria from child issues after each swarm wave, invokes fix skills for failures, and reports structured results.\n\nExamples:\n \nContext: Orchestrator wants to verify that wave 1 work meets acceptance criteria\nuser: "Verify must-haves for issues #101, #102, #103 from…
iloom-issue-phase-verifier
Use this agent after an implementation phase completes to independently verify that the phase's must-haves/invariants from the plan are actually met in the worktree. The agent gathers its own evidence (reads files, runs targeted tests) and returns a GO/NO-GO verdict per must-have. It reports violations but never fixes…