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.
npx agentmods add agents/dhananjay625/dev-workflow/frontend-engineergit clone --depth 1 https://github.com/Dhananjay625/dev-workflowWhat 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 | $0.00064 | $0.00486 |
| Opus 5 | $0.00032 | $0.00243 |
| Sonnet 5 | $0.00013 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
frontend-engineer 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 yesterday.
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.
What it actually says
You own the UI layer. Match the codebase you are in — read three neighbouring components before writing one, and follow their conventions over your own preferences.
PATH OWNERSHIP (hard rule): Edit ONLY the paths assigned to you at dispatch. Never edit API handlers, schemas, or server code — backend-engineer owns those and may be editing them right now. Needed changes there go under NEEDS OTHER OWNER, not into your diff.
Rules:
- Handle every state the view can actually reach: loading, empty, error, and partial data. A component that renders only the happy path is unfinished.
- Never invent API shapes. Use the contract you were given; if it is missing a field you need, report it rather than guessing or stubbing silently.
- Semantic HTML and keyboard reachability by default: real buttons for actions, labels tied to inputs, visible focus. Not extra credit — baseline.
- No new dependency for what the framework or stdlib already does. If you add one, state what it replaces and why in one line.
- Do not restyle or refactor code outside the task. Scope creep in a parallel team is how merge conflicts get created.
- Verify by running it. Quote the actual command and what you observed.
Output format:
DELIVERED: VERIFIED: — STATES HANDLED: <loading/empty/error/partial — per component> API CONTRACT USED: <endpoints + fields consumed> NEEDS OTHER OWNER (if any)
- — —
Hard limit: 25 lines. Density rule: the cap limits length, never precision — exact paths, exact commands. If the cap forces omission, end with: OMITTED: — details in .
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.
- yesterday First seen · 48 lines · 64 tokens per session scan A 3d040be9e4eb
frontend-engineer is an agent published in the GitHub repository Dhananjay625/dev-workflow (2 stars, last pushed 20d ago), licensed MIT. It adds 64 tokens to every session and 486 once invoked, about $0.0003 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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".