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-backendgit 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-backend)<a href="https://agentmods.dev/agents/jeftarmascarenhas/context-mesh/agent-backend"><img src="https://agentmods.dev/badge/agents/jeftarmascarenhas/context-mesh/agent-backend.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.00709 |
| Opus 5 | $0.00000 | $0.00354 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
agent-backend 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] Test: `curl "http://localhost:3000/api/weather?city=London"` returns data How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Backend - Weather App
Purpose
Implement the weather service and API route with Open-Meteo integration (geocoding + weather).
Context Files to Load
- @context/intent/feature-weather-display.md
- @context/decisions/002-api-integration.md
- @context/knowledge/patterns/api-design.md
Scope
- Allowed directories:
backend/src/ - Prohibited: Don't modify frontend
Execution Steps
-
Create Weather Service
- Create
backend/src/services/weather.service.ts - Implement Open-Meteo Geocoding API call (city name → coordinates)
- Implement Open-Meteo Weather API call (coordinates → weather)
- Map WMO weather codes to descriptions and icons
- Handle API errors gracefully
- Transform response to simplified format
- Create
-
Create Weather Route
- Create
backend/src/routes/weather.routes.ts - Implement
GET /api/weather?city={city} - Add Swagger schema documentation
- Register route in
app.ts
- Create
-
Create Types
- Create
backend/src/types/weather.ts - Define request/response interfaces
- Define geocoding and weather API response types
- Create
Expected Output
backend/src/
├── services/
│ └── weather.service.ts
├── routes/
│ └── weather.routes.ts
├── types/
│ └── weather.ts
├── plugins/
│ ├── swagger.ts
│ └── cors.ts
└── app.ts (updated with routes)
API Response Format
// GET /api/weather?city=London
{
"success": true,
"data": {
"city": "London",
"country": "United Kingdom",
"temperature": 15.2,
"description": "Overcast",
"icon": "☁️",
"windSpeed": 8.5,
"windDirection": 180
}
}
Implementation Notes
- Geocoding First: Call
https://geocoding-api.open-meteo.com/v1/search?name={city}&count=1 - Weather Second: Use coordinates from geocoding to call
https://api.open-meteo.com/v1/forecast?latitude={lat}&longitude={lon}¤t_weather=true - Weather Code Mapping: Map WMO weather codes (0-99) to descriptions and icons (see 002-api-integration.md)
- Error Handling: Handle cases where city is not found or API fails
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 · 92 lines · 0 tokens per session scan A af0bfc7552e8
agent-backend 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 709 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.