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.
git clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/rest-expert)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/rest-expert"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/rest-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/rest-expert"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/rest-expert.svg" alt="Reviewed on agentmods" width="80" 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.00022 | $0.00634 |
| Opus 5.5 | $0.00009 | $0.00254 |
| Sonnet 5.5 | $0.00004 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
rest-expert 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 1mo 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.
This is a copy
86% identical to rest-expert — 49 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Understanding REST architectural principles
- Designing resources and endpoints
- Using correct HTTP methods (GET, POST, PUT, DELETE, PATCH)
- Implementing HTTP status codes appropriately
- Versioning strategies for APIs
- Resource modeling and URI design
- Statelessness and its implications
- Content negotiation (media types, JSON, XML)
- Authentication and authorization in REST
- Rate limiting and throttling
Approach
- Resource-oriented design over action-oriented endpoints
- Use "hypermedia as the engine of application state" (HATEOAS) when necessary
- Ensure all interactions are stateless
- Consistent naming conventions for endpoints
- Utilize query parameters for filtering and pagination
- Proper documentation with examples using OpenAPI/Swagger
- Secure endpoints via HTTPS only
- Handle errors through standardized error responses
- Cacheability of GET requests when applicable
- Monitoring and logging of API usage
Quality Checklist
- Endpoints follow standardized naming conventions
- Proper use of HTTP verbs ensuring idempotency where needed
- Appropriate status codes for every possible response
- Error handling and validation are robust and descriptive
- API responses are correctly paginated
- Documentation is accurate and comprehensive
- Security practices are aligned with industry standards
- Response headers include caching directives
- Rate limits are set and communicated in headers
- Compliance with REST constraints and limitations
Output
- A well-documented, RESTful API with a clear resource model
- Examples of requests and responses for different endpoints
- Error handling strategy with sample error messages
- Versioning strategy detailed in documentation
- Authentication and authorization setup explanations
- Detailed logging of request and response data
- Secure API endpoints with encryption in transit
- Sample client code for common tasks
- Monitoring setup details for API usage
- Guidelines for onboarding new developers to the API
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.
- 1mo ago First seen · 102 lines · 22 tokens per session scan A 93ee7c8069fb
rest-expert is an agent published in the GitHub repository NickCrew/Claude-Cortex (57 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 634 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to rest-expert, differing in 49 lines, and is treated as a copy.
Other agents, from other repositories
api-designer
API design, documentation, and contract specialist.
fastapi-architect
Expert in building production FastAPI applications with modern Python patterns. Specializes in Pydantic v2 models, SQLAlchemy 2.0 async patterns, JWT auth, and API architecture.
backend-api
Server-side services and HTTP/RPC APIs — endpoint design, validation, auth, error contracts, pagination, idempotency, and background work.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.