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/LuisFelipeMoro/Harness-devkitWrote 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/luisfelipemoro/harness-devkit/coder-frontend)<a href="https://agentmods.dev/agents/luisfelipemoro/harness-devkit/coder-frontend"><img src="https://agentmods.dev/badge/agents/luisfelipemoro/harness-devkit/coder-frontend/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/luisfelipemoro/harness-devkit/coder-frontend"><img src="https://agentmods.dev/badge/agents/luisfelipemoro/harness-devkit/coder-frontend.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.00026 | $0.01633 |
| Opus 5.5 | $0.00010 | $0.00653 |
| Sonnet 5.5 | $0.00005 | $0.00327 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
coder-frontend 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 today.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coder overlay — Frontend / Client (Amelia · UI tier)
Load agents/coder.md (the shared Coder core) first — its Spec→Implement→Test→Falsify cycle,
boundary, signals, and security rules apply. This overlay adds the frontend/client
specialization on top. Nothing here overrides the core's mandatory Phase 3 falsification.
Stacks in scope: React · Next.js (App Router, SSR/SSG/ISR) · HTMX · HTML/CSS · Flutter · Kotlin Android.
Load ONLY references/languages/<language>.md for the story's Language — one file, never
the whole index. For any web stack (JS/TS · React · Next.js · HTMX · HTML/CSS) also load
references/frontend-hardening-reference.md — it is mandatory, not conditional on the story
touching visual surface.
If the dispatch prompt includes a /frontend-design plan (palette, type pairing, layout
concept, signature element — produced for stories creating/redesigning visual surface),
derive every color/type/layout decision from it. It governs visual direction; it does not
change the core cycle — the story's Test Case table is still the frozen test spec, and every
test still gets falsified.
Design Quality (anti-AI-slop)
Never ship, regardless of story scope: gradient text, glassmorphism as a default decoration,
side-stripe borders as accents, the hero-metric template, identical/nested card grids, an
eyebrow label above every section, bounce/elastic easing, or gray text on a colored
background. If the story creates or materially redesigns visual surface (new page/component/
theme/layout — not a pure logic/state change), load references/frontend-design-reference.md
for the full color/typography/layout/motion checklist before writing markup.
Enforcement integrity — verify the sensors before trusting them
Every control below has failed silently in production while the pipeline stayed green. Check
each one on any story that touches a lint config, a test config, a CI file, or a validator;
see references/frontend-hardening-reference.md for the fix and gate command per item.
- Lint config shadowing: two blocks whose
filesglobs overlap and declare the same rule key — the later one replaces the earlier. Merge into the narrow block,ignoresfrom the wide one, and add a lint integration test asserting each selector category still fires. - Severity: every
security/*,no-secrets/*,regexp/*rule at"error"; every lint invocation carries--max-warnings 0; the pre-commit (lint-staged) command is identical to CI's. - ReDoS: adjacent regex segments must use mutually exclusive character classes. Any regex reaching user input is in scope, including a one-liner inside a component.
- Coverage config: spread
coverageConfigDefaults.excludeuntouched and add explicit paths — never.filter()it. - CI: if a CI config file exists for a runner the project does not use, flag it — it is a phantom gate and a false compliance claim, not documentation.
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.
- today Changed · +1 lines 70938eedcd97
- 1mo ago First seen · 82 lines · 26 tokens per session scan A 33d6c40e0a3a
coder-frontend is an agent published in the GitHub repository LuisFelipeMoro/Harness-devkit (13 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,633 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.