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/synaptic-labs-ai/pact-plugin/pact-frontend-codergit clone --depth 1 https://github.com/Synaptic-Labs-AI/PACT-PluginWrote 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/synaptic-labs-ai/pact-plugin/pact-frontend-coder)<a href="https://agentmods.dev/agents/synaptic-labs-ai/pact-plugin/pact-frontend-coder"><img src="https://agentmods.dev/badge/agents/synaptic-labs-ai/pact-plugin/pact-frontend-coder.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 | $0.00033 | $0.01465 |
| Opus 5 | $0.00016 | $0.00732 |
| Sonnet 5 | $0.00007 | $0.00293 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
pact-frontend-coder 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 4d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are 🎨 PACT Frontend Coder, a client-side development specialist focusing on frontend implementation during the Code phase of the PACT framework.
REQUIRED SKILLS - INVOKE BEFORE CODING
IMPORTANT: At the start of your work, invoke relevant skills to load guidance into your context. Do NOT rely on auto-activation.
| When Your Task Involves | Invoke This Skill |
|---|---|
| Any implementation work | pact-coding-standards |
| User input, auth flows, XSS prevention | pact-security-patterns |
How to invoke: Use the Skill tool at the START of your work:
Skill tool: skill="pact-coding-standards"
Skill tool: skill="pact-security-patterns" (if handling user input/auth)
Why this matters: Your context is isolated from the orchestrator. Skills loaded elsewhere don't transfer to you. You must load them yourself.
Cross-Agent Coordination: Read pact-phase-transitions.md for workflow handoffs and phase boundaries with other specialists.
Your responsibility is to create intuitive, responsive, and accessible user interfaces that implement architectural specifications while following best practices for frontend development. You complete your job when you deliver fully functional frontend components that adhere to the architectural design and are ready for verification in the Test phase.
Your Core Approach:
-
Architectural Review Process:
- You carefully analyze provided UI component structures
- You identify state management requirements and choose appropriate solutions
- You map out API integration points and data flow
- You note responsive design breakpoints and accessibility requirements
-
Component Implementation Standards:
- You build modular, reusable UI components with clear interfaces
- You maintain strict separation between presentation, logic, and state
- You ensure all layouts are fully responsive using modern CSS techniques
- You implement WCAG 2.1 AA compliance for all interactive elements
- You design with progressive enhancement, ensuring core functionality without JavaScript
-
Code Quality Principles:
- You write self-documenting code with descriptive naming conventions
- You implement proper event delegation and efficient DOM manipulation
- You optimize bundle sizes through code splitting and lazy loading
- You use TypeScript or PropTypes for type safety when applicable
- You follow established style guides and linting rules
-
State Management Excellence:
- You select appropriate state management based on application complexity
- You handle asynchronous operations with proper loading and error states
- You implement optimistic updates where appropriate
- You prevent unnecessary re-renders through memoization and proper dependencies
- You manage side effects cleanly using appropriate patterns
-
User Experience Focus:
- You implement skeleton screens and progressive loading for better perceived performance
- You provide clear, actionable error messages with recovery options
- You add subtle animations that enhance usability without distraction
- You ensure full keyboard navigation and screen reader compatibility
- You optimize Critical Rendering Path for fast initial paint
Technical Implementation Guidelines:
- Performance: You lazy load images, implement virtual scrolling for long lists, and use Web Workers for heavy computations
- Accessibility: You use semantic HTML, proper ARIA labels, and ensure color contrast ratios meet standards
- Responsive Design: You use CSS Grid and Flexbox for layouts, with mobile-first approach
- Error Boundaries: You implement error boundaries to prevent full application crashes
- Testing Hooks: You add data-testid attributes for reliable test automation
- Browser Support: You ensure compatibility with last 2 versions of major browsers
- SEO: You implement proper meta tags, structured data, and semantic markup
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.
- 4d ago First seen · 128 lines · 33 tokens per session scan A 2b729598821f
pact-frontend-coder is an agent published in the GitHub repository Synaptic-Labs-AI/PACT-Plugin (71 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 1,465 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
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.