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/jeftarmascarenhas/context-mesh/agent-frontendgit clone --depth 1 https://github.com/jeftarmascarenhas/context-meshWrote 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/jeftarmascarenhas/context-mesh/agent-frontend)<a href="https://agentmods.dev/agents/jeftarmascarenhas/context-mesh/agent-frontend"><img src="https://agentmods.dev/badge/agents/jeftarmascarenhas/context-mesh/agent-frontend.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.1 | $0.00000 | $0.00825 |
| Opus 5 | $0.00000 | $0.00413 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
agent-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 5d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Frontend - Todo App
Purpose
Implement the React frontend with authentication and todo management features.
Context Files to Load
- @context/intent/project-intent.md
- @context/intent/feature-user-auth.md
- @context/intent/feature-todo-crud.md
- @context/decisions/001-tech-stack.md
- @context/knowledge/patterns/api-design.md
Scope
- Allowed:
frontend/src/ - Prohibited: Modify backend code
Execution Steps
-
Create API Service
- Create
frontend/src/services/api.ts - Configure Axios instance
- Set base URL to backend
- Handle credentials (cookies)
- Create
-
Create Auth Context
- Create
frontend/src/context/AuthContext.tsx - Manage user state
- Provide: user, login, logout, signup, isAuthenticated
- Persist auth state
- Create
-
Create Auth Components
- Create
frontend/src/components/auth/LoginForm.tsx - Create
frontend/src/components/auth/SignupForm.tsx - Form validation
- Error handling
- Create
-
Create Todo Components
- Create
frontend/src/components/todos/TodoList.tsx - Create
frontend/src/components/todos/TodoItem.tsx - Create
frontend/src/components/todos/TodoForm.tsx - Create
frontend/src/components/todos/TodoActions.tsx
- Create
-
Create Pages
- Create
frontend/src/pages/Home.tsx - Create
frontend/src/pages/Login.tsx - Create
frontend/src/pages/Signup.tsx - Create
frontend/src/pages/Todos.tsx
- Create
-
Configure Routing
- Setup React Router
- Protected routes for /todos
- Redirect if not authenticated
-
Create Layout
- Create
frontend/src/components/layout/Header.tsx - Create
frontend/src/components/layout/Layout.tsx - Navigation with auth status
- Create
Expected Structure
frontend/src/
├── components/
│ ├── auth/
│ │ ├── LoginForm.tsx
│ │ └── SignupForm.tsx
│ ├── todos/
│ │ ├── TodoList.tsx
│ │ ├── TodoItem.tsx
│ │ ├── TodoForm.tsx
│ │ └── TodoActions.tsx
│ └── layout/
│ ├── Header.tsx
│ └── Layout.tsx
├── context/
│ └── AuthContext.tsx
├── pages/
│ ├── Home.tsx
│ ├── Login.tsx
│ ├── Signup.tsx
│ └── Todos.tsx
├── services/
│ └── api.ts
├── types/
│ ├── auth.ts
│ └── todo.ts
├── App.tsx
└── main.tsx
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.
- 5d ago First seen · 121 lines · 0 tokens per session scan A 3c84b2a682c4
agent-frontend is an agent published in the GitHub repository jeftarmascarenhas/context-mesh (39 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 825 tokens. 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
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
frontend-react-engineer
Specializes in React/TypeScript frontend development following TDD and component-driven development. Uses Specmatic for backend mocking during parallel development.
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…