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-authgit 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-auth)<a href="https://agentmods.dev/agents/jeftarmascarenhas/context-mesh/agent-auth"><img src="https://agentmods.dev/badge/agents/jeftarmascarenhas/context-mesh/agent-auth.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.00000 | $0.00683 |
| Opus 5 | $0.00000 | $0.00342 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
agent-auth scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:3000/api/auth/signup \ How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Authentication - Todo App
Purpose
Implement user authentication with JWT, including signup, login, and logout functionality.
Context Files to Load
- @context/intent/feature-user-auth.md
- @context/decisions/002-auth-approach.md
- @context/knowledge/patterns/api-design.md
- @context/knowledge/anti-patterns/avoid-direct-db.md
Scope
- Allowed directories:
backend/src/,frontend/src/ - Prohibited: Don't modify database schema
Execution Steps
Backend
-
Create Auth Service
- Create
backend/src/services/auth.service.ts - Implement: signup, login, validateToken
- Use bcrypt for password hashing
- Use JWT for tokens
- Create
-
Create Auth DTOs
- Create
backend/src/dto/auth.dto.ts - Define: SignupDto, LoginDto, AuthResponse
- Create
-
Create Auth Middleware
- Create
backend/src/middleware/auth.middleware.ts - Verify JWT token
- Attach user to request
- Create
-
Create Auth Routes
- Create
backend/src/routes/auth.routes.ts POST /api/auth/signupPOST /api/auth/loginPOST /api/auth/logout- Register routes in
app.ts
- Create
Frontend
-
Create Auth Context
- Create
frontend/src/context/AuthContext.tsx - Manage user state and tokens
- Provide login, logout, signup methods
- Create
-
Create Auth Components
- Create
frontend/src/components/auth/Login.tsx - Create
frontend/src/components/auth/Signup.tsx - Create
frontend/src/components/auth/Logout.tsx
- Create
-
Create Auth Pages
- Create
frontend/src/pages/Login.tsx - Create
frontend/src/pages/Signup.tsx
- Create
-
Create API Service
- Create
frontend/src/services/api.ts - Configure Axios with auth interceptor
- Create
API Endpoints
POST /api/auth/signup
Body: { email, password, name }
Response: { user: { id, email, name }, token }
POST /api/auth/login
Body: { email, password }
Response: { user: { id, email, name }, token }
POST /api/auth/logout
Response: { message: "Logged out" }
Definition of Done
- Auth service handles signup, login, logout
- Passwords are hashed with bcrypt
- JWT tokens are generated and validated
- Auth middleware protects routes
- Frontend AuthContext manages state
- Login/Signup forms work
- Token stored in httpOnly cookie or localStorage
- Protected routes redirect to login
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 · 101 lines · 0 tokens per session scan A b216be7c2dc9
agent-auth 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 683 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
polyglot-architect
Cross-language API design and binding parity.
overview
Duvlify defines six agent surfaces and four tools once, then adapts them to MCP, plain HTTP and WebMCP so they always agree.
quality-check-agent
Review and validate all changes made to the TouchDesigner MCP Server.