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-setupgit 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-setup)<a href="https://agentmods.dev/agents/jeftarmascarenhas/context-mesh/agent-setup"><img src="https://agentmods.dev/badge/agents/jeftarmascarenhas/context-mesh/agent-setup.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.00655 |
| Opus 5 | $0.00000 | $0.00328 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
agent-setup 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 3d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Setup - Todo App
Purpose
Initialize the project structure with backend (Express + TypeScript) and frontend (Vite + React + TypeScript).
Context Files to Load
- @context/intent/project-intent.md
- @context/decisions/001-tech-stack.md
Scope
- Allowed: Root project,
backend/,frontend/ - Prohibited: Don't implement features, don't setup database
Execution Steps
-
Create Backend Structure
- Initialize Node.js project with TypeScript
- Configure Express with basic middleware
- Create directory structure (routes, services, middleware, dto)
- Setup Prisma (schema will be created in database phase)
- Create
.env.example
-
Create Frontend Structure
- Initialize Vite + React + TypeScript project
- Configure Tailwind CSS
- Setup React Router
- Create base directory structure (components, pages, services, context)
- Create
.env.example
-
Create Root Files
- Create
.gitignore
- Create
Expected Output
todo-app/
├── backend/
│ ├── src/
│ │ ├── app.ts
│ │ ├── middleware/
│ │ ├── routes/
│ │ ├── services/
│ │ └── dto/
│ ├── prisma/
│ ├── package.json
│ ├── tsconfig.json
│ └── .env.example
├── frontend/
│ ├── src/
│ │ ├── App.tsx
│ │ ├── main.tsx
│ │ ├── components/
│ │ ├── pages/
│ │ ├── services/
│ │ └── context/
│ ├── package.json
│ ├── tsconfig.json
│ └── vite.config.ts
└── .gitignore
Environment Variables
backend/.env.example
DATABASE_URL=postgresql://todoapp:todoapp_password@localhost:5432/todoapp
JWT_SECRET=your-secret-key-here
JWT_EXPIRES_IN=7d
PORT=3000
NODE_ENV=development
frontend/.env.example
VITE_API_URL=http://localhost:3000/api/v1
Definition of Done
- Backend structure created with Express + TypeScript
- Frontend structure created with Vite + React + TypeScript
- Directory structure organized
- Environment variables template created
-
pnpm installruns in both directories - TypeScript compiles without errors
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.
- 3d ago First seen · 101 lines · 0 tokens per session scan A 521b4d0f2052
agent-setup 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 655 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
frontend-react-engineer
Specializes in React/TypeScript frontend development following TDD and component-driven development. Uses Specmatic for backend mocking during parallel development.
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.
polyglot-architect
Cross-language API design and binding parity.
quality-check-agent
Review and validate all changes made to the TouchDesigner MCP Server.
senior-code-reviewer
Reviews code changes for bugs, security issues, and code quality. Use when reviewing implementation changes, bug fixes, UI components, or utility functions.