implement-api-endpoint

A guide for creating REST API endpoints in ASP.NET Core. REST endpoints are web addresses that let applications read or change resources using HTTP requests such as GET, POST, PUT, and DELETE.

In plain words
What is it for?
Use it to add API routes, request and response data objects, MediatR handlers, resource operations, and error handling.
Why use it?
It provides a consistent way to route requests, validate input, keep business logic out of controllers, and return the correct HTTP status codes.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/andresharpe/dotbot/implement-api-endpoint
Any agent
npx skills add andresharpe/dotbot --skill implement-api-endpoint
Clone the repo
git clone --depth 1 https://github.com/andresharpe/dotbot

Made for: Claude Code, Codex.

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 667 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00058 $0.00667
Opus 5 $0.00029 $0.00333
Sonnet 5 $0.00012 $0.00133
Haiku 4.5 $0.00006 $0.00067

Measured 2d ago against content hash 3c6b61134998, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement-api-endpoint 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 2d 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.

content/stacks/dotnet/recipes/skills/implement-api-endpoint/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement API Endpoint

Implement REST API endpoints in ASP.NET Core with thin controllers and service-layer delegation.

Workflow

  1. Define the route — resource-oriented URL following REST conventions
  2. Create request/response DTOs — never expose domain entities
  3. Implement handler — business logic in service layer or MediatR handler
  4. Wire the controller action — validate, delegate, return appropriate status code
  5. Verify — test happy path, validation errors, and error responses

Controller Pattern

[ApiController]
[Route("api/[controller]")]
public class ItemsController : ControllerBase
{
    private readonly IMediator _mediator;
    public ItemsController(IMediator mediator) => _mediator = mediator;

    [HttpGet("{id:guid}")]
    public async Task<IActionResult> GetItem(Guid id)
    {
        var result = await _mediator.Send(new GetItemQuery(id));
        if (result.IsFailure)
            return NotFound();

        return Ok(result.Value);
    }

    [HttpPost]
    public async Task<IActionResult> CreateItem([FromBody] CreateItemRequest request)
    {
        var result = await _mediator.Send(new CreateItemCommand(request));
        if (result.IsFailure)
            return BadRequest(result.Error);

        return CreatedAtAction(nameof(GetItem), new { id = result.Value.Id }, result.Value);
    }

    [HttpDelete("{id:guid}")]
    public async Task<IActionResult> DeleteItem(Guid id)
    {
        var result = await _mediator.Send(new DeleteItemCommand(id));
        return result.IsFailure ? NotFound() : NoContent();
    }
}

Best Practices

  • Thin controllers — delegate all business logic to services or MediatR handlers
  • [ApiController] — enables automatic model validation and [FromBody] inference
  • DTOs for input/output — never return domain entities; map with AutoMapper or manual projection
  • Async everywhere — all I/O-bound actions must use async Task<IActionResult>
  • Problem Details for errors — use RFC 7807 format via ProblemDetails middleware
  • Location header on 201 Created — always return CreatedAtAction or CreatedAtRoute

Read the full file on GitHub · 76 lines

Changes

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.

  1. 2d ago First seen · 76 lines · 58 tokens per session scan A 3c6b61134998

Subscribe to this mod's changes

implement-api-endpoint is a skill published in the GitHub repository andresharpe/dotbot (54 stars, last pushed 5d ago), licensed MIT. It adds 58 tokens to every session and 667 once invoked, about $0.0003 per session on Opus 5. 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.

Related

Other skills, from other repositories

hedgehog-planning-intake

Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…

skyf0xx/hedgehog · 374 tokens

inbound-triage

Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or comments and closes. Not part of the…

skyf0xx/hedgehog · 102 tokens

bmad-product-brief

Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.

skyf0xx/hedgehog · 31 tokens

bmad-revendor

Maintainer-only. Use when re-vendoring vendor-skills/BMAD/ against a newer BMAD-METHOD commit — "update BMAD", "re-vendor BMAD", "bump the BMAD pin". Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.

skyf0xx/hedgehog · 72 tokens

bmad-deep-recon

Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here…

skyf0xx/hedgehog · 167 tokens

conventional-commits

Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward…

skyf0xx/hedgehog · 88 tokens