handler-implementer

handler-implementer is an agent for coding agents from claude-market/marketplace. It costs 17 tokens per session (638 once invoked), scanned A, original, MIT.

A coding agent for implementing Axum HTTP handlers in Rust, using API definitions and generated database code. Axum is a Rust framework for building web services.

In plain words
What is it for?
Use it to implement handlers from OpenAPI endpoint definitions, import generated request and response types, call generated database functions, validate conditions, and return appropriate HTTP errors.
Why use it?
It connects the web endpoint’s input and output types with database functions and applies the business rules described by the API.

Agent

Part of the specforge-backend-rust-axum plugin — 3 agents shipped together

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 agents/claude-market/marketplace/handler-implementer
Clone the repo
git clone --depth 1 https://github.com/claude-market/marketplace

Or install specforge-backend-rust-axum, the plugin that ships this one along with the rest of its 3 agents.

Wrote 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.

agentmods badge for handler-implementer

README.md
[![agentmods](https://agentmods.dev/badge/agents/claude-market/marketplace/handler-implementer.svg)](https://agentmods.dev/agents/claude-market/marketplace/handler-implementer)
Your own site
<a href="https://agentmods.dev/agents/claude-market/marketplace/handler-implementer"><img src="https://agentmods.dev/badge/agents/claude-market/marketplace/handler-implementer.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 638 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.00017 $0.00638
Opus 5 $0.00009 $0.00319
Sonnet 5 $0.00003 $0.00128
Haiku 4.5 $0.00002 $0.00064

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

Security

Grade A, and why

handler-implementer 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.

specforge-backend-rust-axum/agents/handler-implementer.md · 97 lines

How it starts

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

Handler Implementer Agent

You implement HTTP handlers by stitching together OpenAPI-generated types with DB-generated functions.

Your Task

Given:

  1. OpenAPI endpoint definition
  2. Path to generated API types
  3. Path to generated DB functions

Implement the handler function.

Implementation Steps

  1. Determine imports:

    // From OpenAPI generator
    use crate::generated::api::{
        CreateUserRequest,  // From requestBody schema
        User,               // From response schema
        ErrorResponse,      // From error schema
    };
    
    // From codegen plugin
    use crate::generated::db::{
        create_user,
        get_user_by_email,
    };
    
  2. Implement handler signature (using framework patterns from skills):

    pub async fn create_user_handler(
        State(state): State<AppState>,
        Json(payload): Json<CreateUserRequest>,
    ) -> Result<(StatusCode, Json<User>), ErrorResponse>
    
  3. Implement business logic (from OpenAPI description):

    • Parse description for business rules
    • "Check for duplicate email" → call get_user_by_email()
    • Return appropriate error responses (409 for conflict)
  4. Call DB functions:

    let user = create_user(&state.db, &payload.email, &payload.name).await?;
    
  5. Return generated type:

    Ok((StatusCode::CREATED, Json(user)))
    

Example Output

use axum::{extract::State, http::StatusCode, Json};
use crate::{
    generated::api::{CreateUserRequest, User, ErrorResponse},
    generated::db::{create_user, get_user_by_email},
    state::AppState,
};

pub async fn create_user_handler(
    State(state): State<AppState>,
    Json(payload): Json<CreateUserRequest>,
) -> Result<(StatusCode, Json<User>), ErrorResponse> {
    // Business logic: Check for duplicate email
    if get_user_by_email(&state.db, &payload.email).await?.is_some() {
        return Err(ErrorResponse::conflict("Email already exists"));
    }

    // Create user
    let user = create_user(&state.db, &payload.email, &payload.name).await?;

    Ok((StatusCode::CREATED, Json(user)))
}

Read the full file on GitHub · 97 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. 3d ago First seen · 97 lines · 17 tokens per session scan A a8745e8d846a

Subscribe to this mod's changes

handler-implementer is an agent published in the GitHub repository claude-market/marketplace (22 stars, last pushed 10mo ago), licensed MIT. It adds 17 tokens to every session and 638 once invoked, about $0.0001 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 agents, from other repositories

gpui-researcher

Researches and validates GPUI usage patterns, APIs, and conventions. Always checks latest crate version, studies Zed editor and other GPUI projects for real-world patterns. Use when planning or researching GPUI features to ensure implementations match actual API surface and idioms.

Wirasm/prp · 59 tokens

research

Use this agent when the user asks an open-ended question about how the ast-index codebase works ("how is incremental update wired", "why don't we tree-sitter Perl", "what's the data flow for --format json", "which commands share scope filtering"). The agent reads the code, traces connections, and returns a structured…

defendend/Claude-ast-index-search · 103 tokens

rust-quality-gate

Use this agent when code has been written or modified in the Meerkat Rust project and needs to be reviewed for idiomatic Rust quality, correctness, and adherence to project design guidelines. This agent should be invoked after completing a meaningful code change — whether a new function, module, refactor, or bug fix …

lukacf/meerkat · 436 tokens

rust-reviewer

You are a Rust code review agent for the ClaudeTerminal project - a Tauri 2.x desktop application.

talayash/agentrium · 0 tokens

tadpole-backend-specialist

Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.

DDS-Solutions/AI-TadPole-OS · 45 tokens

backend-author

Implements a new poly engine backend end-to-end — empirically checks the upstream crate API, wraps it as a crates.io or pinned-git dependency, implements the Engine trait, registers it, and ships the known-bad + known-unformatted insta fixtures.

Goldziher/poly · 55 tokens