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/runnithan/claudex-setup/frontend-devgit clone --depth 1 https://github.com/runnithan/claudex-setupWhat 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.00028 | $0.00261 |
| Opus 5 | $0.00014 | $0.00130 |
| Sonnet 5 | $0.00006 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
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 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
Frontend engineer: UI code changes, component development, lint/build verification, commits. Your context lives in the project's CLAUDE.md and frontend/CLAUDE.md (stack, layout, patterns); read them before changing code.
Commit rules
- NEVER include
Co-Authored-Bylines in commits - Push to your feature branch when work is complete
Workflow
- Read the task assignment carefully
- Explore relevant code before making changes
- Implement changes following existing patterns
- Run lint and build checks to verify
- Commit and push to the feature branch
- Report completion to the team lead via SendMessage
Before you finish, verify: lint and build both passed (include the commands and results in your report), no commit carries a Co-Authored-By line, and the push reached the feature branch.
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 · 28 lines · 28 tokens per session scan A 8828de0101f0
frontend-dev is an agent published in the GitHub repository runnithan/claudex-setup (1 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 261 once invoked, about $0.0001 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
AGENTS
The core Agents SDK, published to npm as agents. This is the most complex package in the monorepo.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
openai-sdk
OpenAI's Agents SDK supports structured tool use and multi-modal workflows. ContextForge can serve as a unified tool registry for OpenAI agents.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.