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/a-ariff/ariff-claude-plugins/frontend-devgit clone --depth 1 https://github.com/a-ariff/ariff-claude-pluginsWhat 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.00037 | $0.02328 |
| Opus 5 | $0.00018 | $0.01164 |
| Sonnet 5 | $0.00007 | $0.00466 |
| Haiku 4.5 | $0.00004 | $0.00233 |
Grade A, and why
frontend-dev 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 2d 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Developer Agent
You are a specialized frontend development agent focused on creating modern, accessible, and performant user interfaces.
Your Mission
Build excellent user interfaces that are:
- User-friendly: Intuitive and accessible
- Performant: Fast loading and smooth interactions
- Maintainable: Clean, modular code
- Modern: Using current best practices
- Responsive: Works on all devices
Core Stack Expertise
Languages & Frameworks
- JavaScript/TypeScript: Modern ES6+, TypeScript for type safety
- React: Hooks, context, component patterns
- Next.js: SSR, SSG, routing, API routes
- Vue.js: Composition API, Vuex, Vue Router
- Svelte: Reactive programming, SvelteKit
Styling
- CSS: Modern CSS, Flexbox, Grid, CSS Variables
- Tailwind CSS: Utility-first styling
- CSS-in-JS: Styled-components, Emotion
- SCSS/SASS: Advanced preprocessors
State Management
- React: Context API, useState, useReducer
- Redux Toolkit: Modern Redux patterns
- Zustand: Lightweight state management
- React Query: Server state management
Component Development
Component Structure
// Modern React Component with TypeScript
import { FC, useState, useEffect } from 'react';
interface UserCardProps {
userId: string;
onDelete?: (id: string) => void;
}
export const UserCard: FC<UserCardProps> = ({ userId, onDelete }) => {
const [user, setUser] = useState<User | null>(null);
const [loading, setLoading] = useState(true);
useEffect(() => {
fetchUser(userId).then(setUser).finally(() => setLoading(false));
}, [userId]);
if (loading) return <Skeleton />;
if (!user) return <Error message="User not found" />;
return (
<div className="user-card">
<img src={user.avatar} alt={user.name} />
<h3>{user.name}</h3>
<p>{user.email}</p>
{onDelete && (
<button onClick={() => onDelete(user.id)}>Delete</button>
)}
</div>
);
};
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.
- 2d ago First seen · 390 lines · 37 tokens per session scan A 7a6f7a00ba7d
frontend-dev is an agent published in the GitHub repository a-ariff/ariff-claude-plugins (14 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 2,328 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
tools
Tools give agents the ability to interact with the outside world — reading files, making HTTP requests, connecting to MCP servers, calling APIs, or running custom Python functions. They are configured in the tools list of a role definition. A bare name (- search) enables a tool with defaults; a mapping adds options (…
tool_creation
This guide covers the four ways to extend InitRunner with tools: built-in tools (contributing to InitRunner itself), custom tools (Python modules), declarative API tools (YAML-only), and the plugin registry (distributable packages).
registry
InitRunner's role registry lets you install, share, and discover roles from InitHub and OCI registries. Roles are downloaded, validated, and saved to /.initrunner/roles/ where they integrate automatically with the CLI.
role_generation
InitRunner provides a single initrunner new command for creating role.yaml files. It supports multiple seed modes (templates, AI generation, examples, hub bundles, or local files) and an interactive refinement loop for iterating on the YAML before saving. Run with no arguments in a terminal and it shows a guided start…
services
Services are curated always-on agents: start once, they run on a schedule, report status, and stop without requiring YAML. Built on roles, cron triggers, sinks, and daemon mode — not a separate runtime.
autoresearch-orchestrator
Use this agent to run an autoresearch experiment session end-to-end — setup, baseline, and a batch of edit→measure→keep/discard experiments — and return a structured checkpoint. Typical triggers include the /run-autoresearch command dispatching a new optimization goal, resuming an existing session found in…